THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
2. Create a VNF appliance from VNF template
We will need an "Add Appliance" wizard - this will effectively creates a VM, based on "Appliance" templates or ISOs Users be asked to
1. select the Appliance template or ISO.
2. Select the service offering
3. The user would not get options for data disks
4. When adding Networks the user would be informed of the minimum number of NICs required by the template (this is to be implemented as part of multi-disk OVAs) AND the informational text that was supplied when adding the template.
5. The user would be prompted assign any affinity groups
6. The user would be prompted for name and final confirmation.
VNF appliance integration by the cloud operator, for a new VNF the operator must:
...
| Milestone | Planned date | Actual date | |
|---|---|---|---|
| 1 | Start development | 2023-09-01 | 2023-09-1 |
| 2 | main Development is done | 2023-09-15 | 2023-09-22 |
| 3 | dev testing is done | 2023-09-22 | 2023-09-28. PR is created https://github.com/apache/cloudstack/pull/8022 |
| 4 | add marvin/unit test | 2023-09-22 | |
| 5 | Final dev review | 2023-09-27 | |
| 6 | pass over to QA | 2023-09-29 | |
| 7 | QA testing is done | 2023-10-27 |
...
NFV - Network Functions Virtualization
Database Changes
1. vm_template (existing table) Replaced by new template type: VNF
2. vnf_template_nics (new table)
| Column | Type | Comment |
|---|---|---|
id | bigint unsigned NOT NULL AUTO_INCREMENT | id of the NIC |
template_id | bigint unsigned NOT NULL | id of the VNF template |
device_id | bigint unsigned NOT NULL | Device id of the NIC when plugged into the VNF appliances |
device_name | varchar(255) NOT NULL | Name of the NIC |
required | tinyint NOT NULL DEFAULT '1' | True if the NIC is required. False if optional |
description | varchar(255) | Description of the NIC |
3. vnf_template_details (new table)
| Column | Type | Comment |
|---|---|---|
id | bigint unsigned NOT NULL AUTO_INCREMENT | |
template_id | bigint unsigned NOT NULL | id of the VNF template |
name | varchar(255) NOT NULL | |
value | varchar(255) NOT NULL | |
display | tinyint(1) NOT NULL DEFAULT '1' | 'True if the detail can be displayed to the end user' |
Each VNF template can have the following details
access_methods (separated by comma)
- username
- password
- ssh_port
- http_port
- http_path
- https_port
- https_port
resource icon- version
- vendor
- maintainer
Available Access methods are
ssh-with-password (username is required, password is required if template is not password-enabled)
ssh-with-keypair (username is required, keypair is required when deploy VNF appliances)
http (http_path is required. http_port is optional)
https (https_path is required. https_port is optional)
console
| CSS Stylesheet |
|---|
.home-banner {
background: #0052cc;
color: #c2d6d6;
font-size: 20px;
padding: 20px;
}
.home-banner h2 {
color: #f2f2f2;
} |
...
Overview
Content Tools
Apps