-
Story
-
Resolution: Done
-
Medium
-
None
-
None
Duplicate this to OOM-393 and discuss both OPNFV and CNCF there - as the OPNFV plugfest results are uncertain and there may not be enough content for a talk
Handling DCAE
As we all know we will need an openstack lab for bringing up the 3 vFW vms via MSO and for running the 64g DCAEGEN2 VM
For myself, I will likely use Rackspace to bring up the 3 vFW VMs when I am able to hopefully in the next 3 weeks. For DCAEGEN2 we need a decision to help out OPNFV – their case is similar to mine in that they don’t have an OPENLAB to work with.
The big issue is that the only currently working DCAEGEN2 is when everything is run as HEAT in OPENLAB.
We may have 4 options
Option 1: DCAEGEN2 in OPENLAB
My currently limited window into DCAEGEN2 architecture tells me that we need a public openstack for public cloud demos
For demos inside corporate firewalls – we have the same issue as public demos – we need to get through the OPENLAB vpn to get at the recommended DNSaaS designate enhanced openstack running there.
Option 2: DCAEGEN2 in our own openstack lab – with a DNSaaS Designate upgrade – OPNFV is trying to go this route
Option 3: DCAE (gen1) – as suggested
We should try to see if we can get the older containerized dcae we all were working on 3 months ago – to see if we can at least get the 1.0 historical version up (no Openstack required)
Option 4: Run OOM as a 4 node 16g cluster in OPENLAB – then we have direct access to a Designate DCAEGEN2 VM
- mentioned in
-
Page Loading...