Apmec MEA Manager (MEM) component manages the life-cycle of a Virtual Network Function (MEA). MEM takes care of deployment, monitoring, scaling and removal of MEAs on a Virtual Infrastructure Manager (VIM).
TOSCA MEAD templates can be onboarded to Apmec MEAD Catalog using following command:
apmec mead-create --mead-file <yaml file path> <MEAD-NAME>
Note
Users can find various sample TOSCA templates at https://github.com/openstack/apmec/tree/master/samples/tosca-templates/mead
There are two ways to create a MEA in Apmec.
In this method, a TOSCA MEAD template is first onboarded into Apmec MEAD catalog. This MEAD is then used to create MEA. This is most common way of creating MEAs in Apmec.
i). Onboard a TOSCA MEAD template.
apmec mead-create --mead-file <yaml file path> <MEAD-NAME>
ii). Create a MEA.
apmec mea-create --mead-name <MEAD-FILE-NAME> <MEA-NAME>
apmec mead-create --mead-file sample-mead-hello-world.yaml hello-world-mead
apmec mea-create --mead-name hello-world-mead hw-mea
In this method, MEA is created directly from the TOSCA template without onboarding the template into Apmec MEAD Catalog.
apmec mea-create --mead-template <MEAD-FILE-NAME> <MEA-NAME>
This method is recommended when MEM Catalog is maintained outside Apmec and Apmec is primarily used as a MEM workflow engine.
apmec mea-create --mead-template sample-mead-hello-world.yaml hw-mea
Note
mead-list command will show only the onboarded MEADs. To list the MEADs created internally for direct MEA instantiation, use ‘–template-source inline’ flag. To list both onboarded and inline MEADs, use ‘–template-source all’ flag. The default flag for mead-list command is ‘–template-source onboarded’.
apmec mead-list --template-source inline
apmec mead-list --template-source all
Status of various MEM resources can be checked by following commands.
apmec vim-list
apmec mead-list
apmec mea-list
apmec mea-show <MEA_ID>
apmec mead-show <MEAD_ID>
MEAs and MEADs can be deleted as shown below.
apmec mea-delete <MEA_ID/NAME>
apmec mead-delete <MEAD_ID/NAME>
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.