Cisco Cisco Elastic Services Controller 1.1 릴리즈 노트
D R A F T — C I S C O C O N F I D E N T I A L
3
Cisco Elastic Services Controller 1.1 Release Notes
Supported Features
•
Juno on Redhat/RHEL (7.0/7.1)
•
Icehouse on Redhat/RHEL (7.0/7.1)
•
Icehouse on Canonical/Ubuntu (14.0.1)
High Availability (HA)
Cisco Elastic Services Controller Release 1.1 allows you to deploy high availability with database
replication. The database replication is enabled by Distributed Replicated Block Device (DRBD).
replication. The database replication is enabled by Distributed Replicated Block Device (DRBD).
DRBD is used as the replication tool to keep the ESC database synchronized, therefore there is no requirement
of an external storage.
of an external storage.
For more details, see the High Availability chapter in the
ESC Portal
In Cisco Elastic Services Controller Release 1.1, the ESC portal is enhanced to support provisioning for
registration and deployment.
registration and deployment.
•
To register VNFs, choose Resources > Registration.
•
To deploy VNFs, choose Deployments.
The drag and drop feature allows you to grab an existing registration datamodel and to re-use it by
dragging the file to the drop off area.
dragging the file to the drop off area.
Note
The Register or Deploy button will be disabled until the xml file is identified. Only xml files are
accepted.
accepted.
The drag and drop feature executes a REST call as of now and does not execute NETCONF calls. If you
want to delete the registration created through the drag and drop feature then you must do it from either
the ESC Portal or directly through REST call. If you use both REST and NETCONF calls then it will
cause ESC to get out of sync with the registrations.
want to delete the registration created through the drag and drop feature then you must do it from either
the ESC Portal or directly through REST call. If you use both REST and NETCONF calls then it will
cause ESC to get out of sync with the registrations.
For more details, see the ESC Portal chapter in the
Network Enhancement
Cisco Elastic Services Controller Release 1.1 supports creation of both a tenant network and a provider
network.
network.
•
Tenant Network—A tenant network is created for a single network and all its instances. It is isolated
from the other tenants.
from the other tenants.
•
Provider Network—A provider network is created by the administrator. The attributes are mapped
to the physical underlying network or a segment. The following attributes define a provider network:
to the physical underlying network or a segment. The following attributes define a provider network:
–
network_type
–
physical_network
–
segmentation_id
ESC also supports Ephemeral networks which are short-lived tenant networks purposely created during
unified deployment and exists only till the lifetime of that deployment. For more details, see
unified deployment and exists only till the lifetime of that deployment. For more details, see
Cisco Elastic Services Controller Release 1.1 also supports SR-IOV pass-through interfaces. However,
OpenStack should be configured to support SR-IOV pass-through interfaces. ESC introduces new
provider_network type and interface type attributes to support SR-IOV.
OpenStack should be configured to support SR-IOV pass-through interfaces. ESC introduces new
provider_network type and interface type attributes to support SR-IOV.