I does not sound like there is a working demo, that would suit my current setup : ONAP deployed using OOM and master branch.
At this point I am only concerned about instantiating one or a few VNFs as VMs/virtual-networks on Openstack. I have no problem of creating VNFs from scratch (write descriptors and package as CSAR:s etc) as long as I can find the required information somewhere: Some questions that has popped up along my trials are: - How do you use the VNFSDK to create your own VNF CSAR? - A CSAR that has been uploaded to the VNFSDK marketplace, how is that made available from within SDC when you create a service? - Given that you have a VF-C NSD and VNFD, what are the required steps to package, onboard, ... until you have your VMs up an running, and what are the ONAP "components" used within these steps. I would be most grateful for answers to some or all of these questions. /Lars 2018-02-20 0:49 GMT+01:00 Michael O'Brien <[email protected]>: > Sorry for not writing clearly – I was thinking in my head “onap” when I > wrote oom > > > > Hi, There are a multiple levels of working state (onap up, > onap+dcagegen2 up, onap+vnfs, and onap+dcaegen2+vnfs+closedloop) > > > > OOM will deploy all of onap except DCAE via master on any type of > environment > > OOM will deploy all of onap including DCAE vi amsterdam and the heat > side cloudify controller on an openstack environment > > ONAP (whether deployed via OOM or HEAT) will allow for VNF > orchestration via SO with occasional bug workarounds in master/amsterdam > only on openstack until SO/Multicloud brings in cloud-native VNF > orchestration that is in the works. > > The amsterdam branch deploys DCAEGEN2 via OOM only on openstack using > Alexis’s heatbridge between the two dcae controllers on both sides. It > last worked for me before the openlab IP reset last week up to the CDAP > nodes – I fail partway through for now on lack of IPs > > I have not verified closed loop for 2 months. > > > > > > *From:* FREEMAN, BRIAN D [mailto:[email protected]] > *Sent:* Monday, February 19, 2018 11:32 > *To:* Michael O'Brien <[email protected]>; Lars-Erik Helander < > [email protected]>; [email protected] > > *Subject:* Re: [onap-discuss] Working demo ? > > > > Oom is not part of vnf orchestration so you might want to reword that > Michael. Oom only sets up onap. Once onap is up oom is not involved in > onboarding, instantiation or lcm of vnfs > > Brian > > > > > > > > Sent via the Samsung Galaxy S8, an AT&T 4G LTE smartphone > > > > > > -------- Original message -------- > > From: "OBRIEN, FRANK MICHAEL" <[email protected]> > > Date: 2/19/18 10:46 AM (GMT-05:00) > > To: Lars-Erik Helander <[email protected]>, [email protected] > > Subject: Re: [onap-discuss] Working demo ? > > > > Lars, > > Hi, There are a multiple levels of working state (onap up, > onap+dcagegen2 up, onap+vnfs, and onap+dcaegen2+vnfs+closedloop) > > > > OOM will deploy all of onap except DCAE via master on any type of > environment > > OOM will allow for VNF orchestration with occasional bug workarounds in > master/amsterdam only on openstack until SO/Multicloud brings in > cloud-native VNF orchestration that is in the works. > > The amsterdam branch deploys DCAEGEN2 via OOM only on openstack. It > last worked for me before the openlab IP reset last week. > > I have not verified closed loop for 2 months. > > /michael > > > > > > *From:* [email protected] [mailto:onap-discuss-bounces@ > lists.onap.org <[email protected]>] *On Behalf Of *Lars-Erik > Helander > *Sent:* Monday, February 19, 2018 08:57 > *To:* [email protected] > *Subject:* [onap-discuss] Working demo ? > > > > Is there a working demo that could be used on a system deployed via OOM > and master branch? > > > > /Lars > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=VAxZ9H9do7EM1pL_GUqk9dOXOJA7Q9RvUZazNDoLzYI&s=tMgIG2smpj6aeAaXbp3JylwSx2xpXMx2GG42WNE_ipY&e=> > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at https://www.amdocs.com/about/email-disclaimer >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
