Hi Tim, Tacker fuel-plugin used in Colorado release is based on your repo [1]. I see that there are some code changes in tacker newton as part of the implementation of bp tacker-vnffg [2]. So do you have any plans to rebase the SFC_colorado changes to newton? How should we proceed about adding tacker-plugin in Fuel 10.?
[1] https://github.com/trozet/tacker/tree/SFC_colorado [2] https://blueprints.launchpad.net/tacker/+spec/tacker-vnffg Thanks, -Veena On Tue, Jan 31, 2017 at 7:34 AM, Serg Melikyan <[email protected]> wrote: > Hi Georgios, > > Aimee was asking same question couple of weeks ago, and I had added > you in the thread as person originally enabled Tacker in Colorado > release. > > > Possibly this is because in Fuel 10 we are using Ubuntu 16.04 with > systemd instead of 14.04 with upstart? > Seems like so. > > >Will fuel-plugin-tacker be updated for Fuel 10? > It's pretty late in the cycle, so the only way Tacker might be added > to Fuel is through feature freeze exception and fixing it quickly. Do > you want to work on that? > > > On Mon, Jan 30, 2017 at 12:33 AM, Paraskevopoulos Georgios > <[email protected]> wrote: > > Hi all, > > > > > > > > I’m trying to deploy Fuel 10 with Tacker plugin enabled and I’m getting > the > > following error: > > > > (/Stage[main]/Tacker::Service/Service[tacker]) Provider upstart is not > > functional on this host > > > > > > > > Possibly this is because in Fuel 10 we are using Ubuntu 16.04 with > systemd > > instead of 14.04 with upstart? > > > > Will fuel-plugin-tacker be updated for Fuel 10? > > > > > > > > Thanks, > > > > George > > > > > > > > > > > > > > > > George Paraskevopoulos > > > > Software Engineer (SDN/NFV), INTRACOM-TELECOM > > > > + 30 210 667 7689 > > > > [email protected] > > > > 19.7 km Markopoulou Ave 19002 Peania, Athens, Greece > > > > > > > > The information in this e-mail message and any attachments are intended > only > > for the individual or entity to whom it is addressed and may be > > confidential. If you have received this transmission in error, and you > are > > not an intended recipient, be aware that any copying, disclosure, > > distribution or use of this transmission or its contents is prohibited. > > INTRACOM TELECOM and the sender accept no liability for any loss, > disruption > > or damage to your data or computer system that may occur while using data > > contained in, or transmitted with, this email. Views or opinions > expressed > > in this message may be those of the author and may not necessarily > represent > > those of INTRACOM TELECOM. > > > > > > > > > > _______________________________________________ > > opnfv-tech-discuss mailing list > > [email protected] > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > > > -- > Serg Melikyan, Development Manager at Mirantis, Inc. > http://mirantis.com | [email protected] | +1 (650) 440-8979 >
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
