Re: [openstack-dev] [Tacker] Proposing yanxingan for Tacker core

[Sridhar Ramaswamy]

+2

Thanks Yan for your contribution to Tacker.

On Jul 27, 2017 10:15 AM, "gongys2017"  wrote:


I am proposing we add Yan xingan as a Tacker core.

Yanxingan is woking in china mobile, a telecom company which has big
requirement
on NFV MANO. We are proud of having him on tacker team, and promoting the
usage of
tacker in his company.

In not long time, he has contributed lots on project, such as review, BP
and active in tacker project meeting.
he has also done presentation on tacker to make propaganda of this project.

Tacker cores, please respond with your opinion. If no reason is given to do
otherwise, I will add Yan xingan to the core group in one week.

Thanks,
Yong Sheng Gong


[1] https://review.openstack.org/#/q/owner:yanxingan%2540cmss.
chinamobile.com


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Tacker] Not able to run user_data commands on my instance

[Sridhar Ramaswamy]

Hi Vishnu,

Just to rule out any underlying metadata service issue, can you verify if a
simple heat stack with user_data [1] works fine first? Also, the actual
TOSCA -> HOT translated template will be available in tacker.log. Try
creating a heat stack using that HOT template and make sure the intended
user_data cmds gets executed..

HTH,
Sridhar

[1]
https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#user-data-boot-scripts-and-cloud-init


On Mon, May 22, 2017 at 5:08 AM, Vishnu Pajjuri 
wrote:

>  Hi,
>
>I'm have installed openstack with tacker by devstack.
>
> I'm able to run OpenWRT vnf and able to configure the firewall service
> with openwrt management driver.
>
> And also able to run shell commands in cirros image which is also using
> openwrt management driver.
>
>
> Now I have created one ubuntu image, and able to launch through tacker.
>
> In this instance i want run some shell commands through tacker's user_data
> feature.
>
> But no commands are executing.
>
> Is it possible to run commands on custom images unlike cirros/openwrt?
>
> If yes kindly share the procedure to create proper ubuntu image.
>
>
>
> Below is tosca configd file
>
>
> tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0
>
> description: Demo with user-data
>
> metadata:
>   template_name: sample-vnfd-userdata
>
> topology_template:
>   node_templates:
> VDU1:
>   type: tosca.nodes.nfv.VDU.Tacker
>   capabilities:
> nfv_compute:
>   properties:
> num_cpus: 1
> mem_size: 1024 MB
> disk_size: 1 GB
>   properties:
> image: ubuntu-image
> config: |
>   param0: key1
>   param1: key2
> mgmt_driver: openwrt
> config_drive: true
> user_data_format: RAW
> user_data: |
>   #!/bin/sh
>   echo "my hostname is `hostname`" > /tmp/hostname
>   date > /tmp/date
>   ifconfig > /tmp/ifconfig
>   df -h > /tmp/diskinfo
> CP1:
>   type: tosca.nodes.nfv.CP.Tacker
>   properties:
> management: true
> order: 0
> anti_spoofing_protection: false
>   requirements:
> - virtualLink:
> node: VL1
> - virtualBinding:
> node: VDU1
>
>  VL1:
>   type: tosca.nodes.nfv.VL
>   properties:
> network_name: net_mgmt
> vendor: ACME
>
> Regards,
> -Vishnu
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Tacker][OSC] Command naming specs

[Sridhar Ramaswamy]

Hi Jay,

See inline ...

On Fri, Apr 14, 2017 at 12:25 PM, Jay Pipes  wrote:

> On 04/12/2017 03:08 AM, Trinath Somanchi wrote:
>
>> Hi OSC team-
>>
>> While  implementing tacker-cli commands as OSC plugins [1], We are
>> struck in command naming specifications.
>>
>> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
>> prefix.
>>
>
> It's not *all* of NFV, though.
>

I agree 'nfv' is an umbrella term and it has significance for other
projects as well (like nova).


>
> This problem, by the way, is an indication that Tacker might have too big
> a scope...and a scope that is very much tailored/purpose-built for
> Telcos/NFV. But whatever, I raised this concern during the project
> application as a member of the TC and folks ignored me, so it is what it is
> I guess.


Will stay away from this as we have thrashed this 'scope' question enough
in the TC discussions :)

However, one thing we are forcing ourselves is not use the 'network' as
initial keyword as it clearly belongs in the realm of neutron and its
associated features. What we are looking for is a term like "stack" that
indicates Orchestration (via Heat project) that we slide under.


>
> We were struck in naming the below commands while aligning with the OSC
>> naming specs.
>>
>> For the below commands, for readability, we have added ‘-‘ within the
>> command names.
>>
>> Like,
>>
>>   network-service,  vnf-forwarding-graph, service-function-chain,
>>
>> network-flow-classifier, network-forwarding-path.
>>
>
> I think what Dean and Akihiro were suggesting is to use "vnf" as the first
> "word" in the command list and then use space-delimited commands like so:
>
> openstack vnf network service create
>
> Or just leave off the "network" above, because, well, Tacker doesn't
> create any other type of service..., so:
>
> openstack vnf service create
>


I like this suggestion. Keyword 'vnf' is the closest to the unit of things
orchestrated by Tacker. Building on that we can have,

openstack vnf create - *create a single VNF based on TOSCA template*
openstack vnf service create - *create a service using a collection of VNFs*
openstack vnf graph create - *create a forwarding graph using a collection
of VNFs*
...


>
> and then
>
> openstack vnf forwardinggraph create
>
> and
>
> openstack vnf service function chain create
>
> but then, you'll hit on the obvious overlap with networking-sfc, which
> will bring in the obvious question of "what's the difference between
> Tacker's SFC and networking-sfc's SFC?" which again should lead folks to
> question the scope of Tacker in relation to other OpenStack projects...
>

It is not an overlap per-se, it is more at a different abstraction level.
The later is a general purpose, lower-level SFC API based on neutron ports.
Former is a higher level YAML (TOSCA) template based description of a SFC
specially geared for NFV use-cases - implemented using the lower-level
networking-sfc APIs. It is analogous to Heat OS::Nova::Server <-> Nova
Compute APIs.

- Sridhar


>
> Best,
> -jay
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [mistral] Using mistral to start a not-to-die task

[Sridhar Ramaswamy]

Renat:

Perfect. A combination of 1 and 2a would fit our needs.

One reason we are venturing toward an async workflow is to address the
scale limitation in tacker. Now, do you've some pointers how well mistral
scales (so that we don't just move our scale problem down to the mistral
dependency). Looking at the mistral architecture [*], is it safe to assume
the individual mistral components like api, engine, scheduler, executor can
be linearly scaled across different hosts ?

- Sridhar

[*] https://docs.openstack.org/developer/mistral/architecture.html

On Wed, Mar 22, 2017 at 11:22 PM, Renat Akhmerov 
wrote:

> Another option:
>
> 1. Run a workflow with a loop (i.e. task calls itself), in order to have a
> delay between task executions you can use either wait-before/wait-after
> task policies
> 2.a The workflow can be stopped via Mistral API by a 3rd party, if needed.
> 2.b The workflow can have a special task that checks if it still needs to
> be running (i.e. making a request to a 3rd party), it can be done using
> conditional transitions
>
>
> Renat Akhmerov
> @Nokia
>
> On 23 Mar 2017, at 09:40, Lingxian Kong  wrote:
>
> Yeah, as Bob said, cron-trigger is what you are looking for.
>
> As our discussion on IRC, currently, Mistral doesn't support to execute
> shell command directly, my suggestion is, you could consider using http
> action (which is supproted by Mistral out of the box) or providing a host
> (physical or virtual) to run 'ping' command and use ssh action in Mistral.
>
>
> Cheers,
> Lingxian Kong (Larry)
>
> On Thu, Mar 23, 2017 at 1:16 PM, gongys2017  wrote:
>
>> Hi mistral stackers,
>>
>> Tacker is using the mistral as its part of system. Now we have a
>> requirement:
>>
>> tacker server registers an openstack as its NFVI, and needs to ping> http-ping) the openstack's management IP,
>> for example the keystone URL until tacker updates or delete the openstack
>> NFVI.
>>
>> Can the mistral be asked to start a workflow which  contains  just such a
>> kind of task:
>> for ever running until extenal tells him to stop.
>>
>>
>> Thanks
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Final mascot files

[Sridhar Ramaswamy]

Hi Tackers,

We got the "final" version of Tacker logo from Openstack marketing team.
Please take a look at the dropbox link below:





*I’m excited to finally be able to share final project logo files with you.
Inside this folder, you’ll find full-color and one-color versions of the
logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use
them on presentations and wherever else you’d like to add some team flair.
https://www.dropbox.com/sh/yyt1lazllah7ccf/AACkW8LkIiG32OXLYBqeP-RJa?dl=0
At
the PWG, we’ll have stickers for your team of the mascot, plus signage on
your room. I’m especially excited for the project teams to see all of the
logos together as one group, because they work beautifully together
stylistically while making each project’s mark distinctive.*

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Virtual PTG Meetup - Wed Feb 22

[Sridhar Ramaswamy]

Folks -

Tacker team will meet virtually for upcoming Pike PTG. Given the
global audience, we will do one 5 - 6 hour conference call starting
Wednesday, February 22, 2017 -  05:00:00 UTC [1]. Please mark your
calendars.

Here is the PTG etherpad [2]. Feel free to add topics and candidate
pike tasks in the etherpad.

- Sridhar

[1] 
https://www.timeanddate.com/worldclock/meetingtime.html?iso=20170222=283=33=235=176
[2] https://etherpad.openstack.org/p/tacker-pike-grooming

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Tacker Mascot

[Sridhar Ramaswamy]

Tackers,

I received a draft version of our project logo, using the mascot we
selected together. A final version will be ready for us before the Project
Team Gathering in February. Before they make our logo final, they want to
be sure we're happy with our mascot.

Let me know if anyone have suggestions to change. We can briefly discuss
this in our meeting today.

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Infra][Tacker] Creating feature branch for Tacker

[Sridhar Ramaswamy]

Adding openstack-infra ...

On Mon, Jan 30, 2017 at 6:10 PM, Digambar Patil  wrote:
> Hello Infra team,
>
> I am implementing new API framework in tacker based on Falcon. We have
> decided to create separate branch for this so that we can push all the code
> to feature branch and once dev is completed, will merge branch to master. So
> we need to create Feature/branch in Tacker.
>
> Reference Spec - https://review.openstack.org/#/c/368511/ - submitted
>
> Can someone help create feature branch from Infra team ?
>
> Thanks,
> Digambar
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Cancelling today's weekly meeting

[Sridhar Ramaswamy]

I'm cancelling today's meeting. We have a light agenda and our
contributors from China are off due to holiday week there. Please use
the extra time to continue to wrap up remaining Ocata items,

- VNFC support
- VNF inline templates
- Pending NSD work (api-ref, samples, etc)
- other pending items listed in your respectives BPs [1]

I'll be available in the #tacker channel for any questions or issues.

thanks,
Sridhar

[1] https://blueprints.launchpad.net/tacker/ocata

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Core team changes / proposing Dharmendra Kushwaha

[Sridhar Ramaswamy]

Thanks for those who responded.

Dharmendra - welcome to the tacker-core team!

- Sridhar

On Tue, Jan 24, 2017 at 4:58 PM, Sridhar Ramaswamy <sric...@gmail.com> wrote:
> Tackers,
>
> I'd like to propose following changes to the Tacker core team.
>
> Stephen Wong
>
> After being associated with Tacker project from its genesis, Stephen
> Wong (irc: s3wong) has decided to step down from the core-team. I
> would like to thank Stephen for his contribution to Tacker,
> particularly for his help navigating the initial days splitting off
> Neutron and in re-launching this project in Vancouver summit for
> TOSCA-based NFV Orchestration. His recent effort in writing the SFC
> driver to support VNF Forwarding Graph is much appreciated. Thanks
> Stephen!
>
> Dharmendra Kushwaha
>
> It gives me great pleasure to propose Dharmendra (irc:  dkushwaha) to
> join the Tacker core team. Dharmendra's contributions to tacker
> started in Jan 2016. He is an active contributor across the board [1]
> in bug fixes, code cleanups and, most recently, as a lead author of
> the Network Services Descriptor blueprint.
>
> Also, Dharmendra recently stepped up to take care of bug triage for
> Tacker. There is an uptick in deployment issues reported through LP
> [2] and in irc - which itself is a good healthy thing. Now we need to
> respond by fixing the issues reported promptly. Dharmendra’s help will
> be immensely valuable here.
>
> Existing cores - please vote +1 / -1.
>
> thanks,
> Sridhar
>
> [1] 
> http://stackalytics.com/?module=tacker-group_id=dharmendra-kushwaha=marks
> [2] https://answers.launchpad.net/tacker

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-sfc]

[Sridhar Ramaswamy]

Networking-sfc features are available to orchestrate using a TOSCA
template through Tacker. The feature is called VNF Forwarding Graph
(VNFFG) and it is available both through tacker cli and horizon
screens.

See tacker docs here for more details,

http://docs.openstack.org/developer/tacker/devref/vnffg_usage_guide.html
http://docs.openstack.org/developer/tacker/devref/vnffgd_template_description.html

On a different note, the last I tried, I also used that setting to get
sfc working on Ubuntu 16.04 devstack,

# Enable networking-sfc
SFC_UPDATE_OVS=False
enable_plugin networking-sfc https://git.openstack.org/openstack/networking-sfc



On Tue, Jan 24, 2017 at 5:30 AM, Bernard Cafarelli  wrote:
> On 20 January 2017 at 00:06, Michael Gale  wrote:
>> Hello,
>>
>> Are there updated install docs for sfc? The only install steps for a
>> testbed I can find are here and they seem outdated:
>> https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining
> There is also a SFC chapter in the networking guide:
> http://docs.openstack.org/newton/networking-guide/config-sfc.html
>
> Which parts do you find outdated? Some references to Ubuntu/OVS
> versions may need a cleanup, but the design and API parts should still
> be OK
> (OSC client, SFC graph API, symmetric ports and other goodies are
> still under review and not yed merged)
>
>> Also from the conference videos there seems to be some Horizon menu /
>> screens that are available?
> Not for networking-sfc directly, but there is a SFC tab in the tacker
> horizon plugin (or will be, someone from the tacker team can confirm
> that)
>
>
> --
> Bernard Cafarelli
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Core team changes / proposing Dharmendra Kushwaha

[Sridhar Ramaswamy]

Tackers,

I'd like to propose following changes to the Tacker core team.

Stephen Wong

After being associated with Tacker project from its genesis, Stephen
Wong (irc: s3wong) has decided to step down from the core-team. I
would like to thank Stephen for his contribution to Tacker,
particularly for his help navigating the initial days splitting off
Neutron and in re-launching this project in Vancouver summit for
TOSCA-based NFV Orchestration. His recent effort in writing the SFC
driver to support VNF Forwarding Graph is much appreciated. Thanks
Stephen!

Dharmendra Kushwaha

It gives me great pleasure to propose Dharmendra (irc:  dkushwaha) to
join the Tacker core team. Dharmendra's contributions to tacker
started in Jan 2016. He is an active contributor across the board [1]
in bug fixes, code cleanups and, most recently, as a lead author of
the Network Services Descriptor blueprint.

Also, Dharmendra recently stepped up to take care of bug triage for
Tacker. There is an uptick in deployment issues reported through LP
[2] and in irc - which itself is a good healthy thing. Now we need to
respond by fixing the issues reported promptly. Dharmendra’s help will
be immensely valuable here.

Existing cores - please vote +1 / -1.

thanks,
Sridhar

[1] 
http://stackalytics.com/?module=tacker-group_id=dharmendra-kushwaha=marks
[2] https://answers.launchpad.net/tacker

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Tacker PTL Non-candidacy

[Sridhar Ramaswamy]

As I announced in the last Tacker weekly meeting, I'm not planning to run
for Pike PTL position. Having served in this role for the last three cycles
(including for the periods before it was a big-tent project), I think it is
time for someone else to step in and take this forward. I'll continue to
contribute as a core-team member. I'll be available to help the new PTL in
any ways needed.

Personally, it has been a such a rewarding experience. I would like to
thank all the contributors - cores and non-core members - who supported
this project and me. We had an incredible amount of cross-project
collaboration in tacker, with the likes of tosca-parser / heat-translator,
neutron networking-sfc, senlin, and mistral - my sincere thanks to all the
PTLs and the members of those projects.

Now going forward, we have tons to do in Tacker - towards making it a
leading, community built TOSCA Orchestrator service. And that, not just for
the current focus area of NFV but also expand into Enterprise and Container
use-cases. Fun times!

thanks,
Sridhar
irc: sridhar_ram
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] December 28th weekly meeting cancelled

[Sridhar Ramaswamy]

We are skipping next week's Tacker meeting, on Dec 28th [1]. We will resume
on Jan 4th.

Happy Holidays!!

[1]
http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-12-21-05.30.log.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Weekly meeting agenda - Dec 14, 2016

[Sridhar Ramaswamy]

Here is the agenda for today's tacker weekly meeting,

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_14th.2C_2016


   - Announcements
   - Spec-less blueprints rundown
  -
  
https://blueprints.launchpad.net/tacker/+spec/deprecate-legacy-template-dsl
(need
  owner)
  - https://blueprints.launchpad.net/tacker/+spec/switch-to-keystoneauth
  - https://blueprints.launchpad.net/tacker/+spec/vnffgd-param-support
  - https://blueprints.launchpad.net/tacker/+spec/hot-template-support
   - Refactor openstack driver (Haiwei) -
   https://review.openstack.org/405276
   - Tacker-Senlin integration spec (Haiwei / Xuan) -
   https://review.openstack.org/#/c/352943/



*Again, please note the new meeting time,*

*Dec 14th, Wednesday 05:30 UTC @ #openstack-meeting.*

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Weekly meeting time slot - doodle poll

[Sridhar Ramaswamy]

Thanks for the all those who responded. There is an overwhelming response
to go with an early UTC time. I'm picking the following slot,

Wednesdays 0530 UTC

I've pushed a request to switch to new this time effective Dec 14th [1]. We
will continue with use the existing Tuesdays 1600UTC slot for one more week
(Dec 6th).

[1] https://review.openstack.org/406390

On Tue, Nov 29, 2016 at 10:17 PM, Sridhar Ramaswamy <sric...@gmail.com>
wrote:

> Given the natural changes in the mix of our active members and the recent
> daylight savings time change, I'm opening a doodle poll to find the best
> slot for our weekly meeting with max coverage. Please respond to the doodle
> poll below,
>
> http://doodle.com/poll/ee9p34kfhskd2ucc
>
> Note, this is the same poll shared in today's weekly meeting, though I've
> added more timeslots to pick from. If you've already responded, please log
> back one more time and select all possible slots.
>
> thanks,
> Sridhar
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Weekly meeting time slot - doodle poll

[Sridhar Ramaswamy]

Given the natural changes in the mix of our active members and the recent
daylight savings time change, I'm opening a doodle poll to find the best
slot for our weekly meeting with max coverage. Please respond to the doodle
poll below,

http://doodle.com/poll/ee9p34kfhskd2ucc

Note, this is the same poll shared in today's weekly meeting, though I've
added more timeslots to pick from. If you've already responded, please log
back one more time and select all possible slots.

thanks,
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Removing required port-id from classifier

[Sridhar Ramaswamy]

Hi Cathy,

See inline...

On Tue, Oct 4, 2016 at 2:36 PM, Cathy Zhang <cathy.h.zh...@huawei.com>
wrote:

> Hi Tim,
>
> Please see inline.
>
> Cathy
>
> -Original Message-
> From: Tim Rozet [mailto:tro...@redhat.com]
> Sent: Tuesday, October 04, 2016 1:29 PM
> To: Cathy Zhang
> Cc: OpenStack Development Mailing List (not for usage questions); Sridhar
> Ramaswamy; Sripriya Seetharam; Anil Vishnoi
> Subject: Re: Removing required port-id from classifier
>
> Responses inline.
>
> Thanks,
>
>
> Hi Cathy,
> I recall a while back discussing removing the required neutron port-id
> from the classifier.
>
> Cathy> Do you mean logical source port here?
> trozet> yeah the neutron_source_port seems required.
>
> Cathy> This is only required if the backend is OVS SFC driver (not
> required if it is ODL SFC driver or other drivers). There are several
> reasons for this. For example, without neutron source port being specified,
> we have to install flow classification rules on every compute node to catch
> the traffic flow from the source and scalability will be a big issue if
> there are thousands of compute nodes. Another example is that if two
> tenants use a shared network and each has its flow originating from
> different source VMs and going through its own SFC in the shared network,
> OVS needs different logical source ports to distinguish different tenants'
> traffic flow. Is there any reason why you can not specify a neutron source
> port?
>

The reason is - this restriction makes orchestrating service-chains very,
very difficult :(

With Tacker VNFFG feature you can neatly describe your waypoints and
classifier in a TOSCA yaml descriptor. Now, this restriction forces the
"operator" to select a specific neutron-port uuid among the possibly 100s
of ports as a "source". This negatively impacts usability and dilutes the
benefit the orchestration solution brings.

If scalability is an issue, instead forcing the higher layers to pick a
specific source-port, I'd suggest n-sfc team to look into coarse-grain
"source identifier" - like CIDR, neutron-network, etc. You should be able
to figure out specific compute-hosts where such VM's vif getting plugged
into neutron and apply the classification rules only on those compute nodes?

- Sridhar


>
>
> We just finished up implementing VNFFG in Tacker and are hitting this
> while testing.  What is the plan to remove this requirement?  Also, how are
> IETF SFC/NSH related API/plugin changes going?  Can we expect to have
> attributes like path-id, encap type soon?
>
> Cathy> The API already provides a way for specifying "path-id" and encap
> type (currently only MPLS encap type is supported since OVS does not
> support NSH yet). As to NSH support, the code patch is being worked on, not
> completed yet. We are also tracking the NSH work in OVS and hope OVS will
> support NSH soon so that when networking-sfc integrates with that new
> version of OVS, NSH can be supported properly.
> trozet> OK good. Anil is close (demoed at ODL summit) a networking-odl
> driver for networking-sfc that supports NSH.
> Can you link the patches or point me to who is working on the NSH support
> for the API/plugin DB layer?
>
> Cathy> Here is the patch link https://review.openstack.org/#/c/373465/
>
>
>
>
> Thanks,
>
> Tim Rozet
> Red Hat SDN Team
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Newton retrospective - notes

[Sridhar Ramaswamy]

Tackers -

I've captured the notes from newton retrospective topic from last week's
meeting,

https://etherpad.openstack.org/p/tacker-newton-retrospective

Let's make Ocata dev cycle even better!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker][ptl] Leave of Absence

[Sridhar Ramaswamy]

Tackers,

I'd like to inform I'll be away from work / the community for about 4 - 6
weeks to attend to an urgent medical need.  This also means I won't be able
to attend the upcoming Barcelona summit. I'll terribly miss the event,
particularly meeting some of the new faces in the Tacker community.

I'm happy that the Newton release is behind us, and Ocata summit planning
is well underway [1]. I'd like to nominate tacker core Sripriya Seetharam
(irc: sripriya) as the acting PTL to continue the work forward in my
absence .

thanks,
Sridhar

[1] https://etherpad.openstack.org/p/tacker-ocata-summit
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] PTL candidacy

[Sridhar Ramaswamy]

Hi Tackers,

I would like to announce my candidacy to continue as Tacker PTL for the
Ocata
dev cycle.

I'm a member of the Tacker community right from its Neutron ServiceVM days.
I actively participated in its transition into NFV Orchestration area and
its
graduation into big-tent. Since becoming an official project our developer
community has grown and has more diverse [1].

Newton was a packed cycle for us with many stellar achievements from the
community: VNF Scaling, Audit Events, VNF Forwarding Graph using Neutron
Networking-SFC (we are almost there!) and External Alarm-based Monitoring
using Ceilometer. As usual tons of refactoring work happened to continue
to shed the "Neutronisms" in the project.

Along the way, we have become a better openstack citizen following best
practices like Reno release-notes, better release processes, and better
python3 support. We also expanded our core-team with three new members.

My vision for Tacker Ocata is along the following workstreams identified
in the recent weekly meeting.

* Decomposed VIM drivers:
We need to enable a healthy ecosystem of VIM drivers beyond the current
default openstack VIM driver. Our user community has mixed hypervisor/cloud
technology in their deployments - with some existing pre-openstack systems
(a.la, VMware), some OpenStack based clouds, and, forward looking into
Containers and public clouds. All this needs an easy to add VIM driver to
bolt underneath Tacker. Luckily our architecture is designed with this in
mind right from day one. We just need to make it easy (a) for developers to
bring in new VIM drivers and (b) for deployers to quickly add new VIM
capabilities without requiring a fork-lift upgrade of Tacker for every new
VIM type.

As part of this workstream, I'd work towards bringing in a Container VIM
type interfacing with Magnum / Zun.

Lifecycle Features:
* Finish left over Newton features - VNFC and NSD
* Better integration with external EM / FCAPS systems
* Enable support for VNFs leveraging Neutron's latest VLAN aware VM feature

Project maintenance:
 * Doc: API reference guide
 * Pecan API framework
 * OSC support
 * Finish python3x TC goal

Tons of fun things to do! However, Ocata is going to be a short cycle.
So, over next few weeks, I'll help to continue to groom these topics and
zoom in on those that are implementable in one dev cycle and clearly
identify some tracks that would carry over to the next cycle.

In Ocata, given an opportunity to serve as your PTL, I'll continue my role
as the "chief enabler" for this amazing community of developers that I'm so
proud to lead over the last two cycles.

- Sridhar Ramaswamy (irc: sridhar_ram)

[1] http://stackalytics.com/?module=tacker-group=commits
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [opentack-dev][tacker]Manual install Tacker fails

[Sridhar Ramaswamy]

Hi Zhi,

Thanks for reporting this issue. This is caused due to a recent code
change, that shows up only during manual install. Please open a bug. Fix is
fairly straightforward.

- Sridhar

On Sun, Sep 11, 2016 at 8:39 PM, zhi  wrote:

> hi,
>
> I downloaded the code from the master branch and installed Tacker manual
> by the document[1]. I met an error when I started the tacker-server by
> "python /usr/bin/tacker-server --config-file /etc/tacker/tacker.conf
>   --log-file /var/log/tacker/tacker.log".
>
> The error message is "
> 2016-09-12 11:20:48.427 ERROR stevedore.extension
> [req-4799662d-a606-4337-802f-d94c44b35a50 None None] Could not load
> 'noop': Can't instantiate abstract class DeviceNoop with abstract methods
> get_resource_info
> 2016-09-12 11:20:48.428 ERROR stevedore.extension
> [req-4799662d-a606-4337-802f-d94c44b35a50 None None] Could not load
> 'nova': Can't instantiate abstract class DeviceNova with abstract methods
> get_resource_info
> "
>
> Did anyone meet the same error as me?
>
> Hope for your reply.
>
>
> Thanks
>
>
> [1]. http://docs.openstack.org/developer/tacker/install/
> manual_installation.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] tacker vnf-create is not bringing upalltheinterfaces

[Sridhar Ramaswamy]

Both OpenWRT or Cirros images just brings up their first interface (eth0)
to automatically do DHCP (client). Either case, please reach out to us in
the #tacker IRC channel to get some help resolving this issue.

On Mon, Aug 29, 2016 at 5:27 AM, Abhilash Goyal 
wrote:

> Default cirros that is added at the time of installation.
> On 29 Aug 2016 16:25, "Zhi Chang"  wrote:
>
>> My cirros image works ok. What version about your cirros image?
>>
>>
>> -- Original --
>> *From: * "Abhilash Goyal";
>> *Date: * Mon, Aug 29, 2016 06:43 PM
>> *To: * "OpenStack Development Mailing List (not for usage questions)"<
>> openstack-dev@lists.openstack.org>;
>> *Subject: * Re: [openstack-dev] tacker vnf-create is not bringing
>> upalltheinterfaces
>>
>> Hello Chang,
>> thanks a lot, this image worked. Could you guide me the same for cirros
>> image.
>>
>>
>> On Mon, Aug 29, 2016 at 2:54 PM, Zhi Chang 
>> wrote:
>>
>>> OpenWRT image should be enabled first nic's DHCP.
>>>
>>>
>>> -- Original --
>>> *From: * "Abhilash Goyal";
>>> *Date: * Mon, Aug 29, 2016 05:35 PM
>>> *To: * "OpenStack Development Mailing List (not for usage questions)"<
>>> openstack-dev@lists.openstack.org>;
>>> *Subject: * Re: [openstack-dev] tacker vnf-create is not bringing up
>>> alltheinterfaces
>>>
>>> Hi Chang,
>>>
>>> I am using https://downloads.openwrt.org/chaos_calmer/15.05/x86/k
>>> vm_guest/openwrt-15.05-x86-kvm_guest-combined-ext4.img.gz image of
>>> openWRT.
>>> This feature is not working for Cirros either.
>>>
>>> On Mon, Aug 29, 2016 at 2:25 PM, Zhi Chang 
>>> wrote:
>>>
 Hi, Goyal.

 What version about your OpenWRT image? You can get OpenWRT image
 from  this: https://drive.google.com/open?id=0B-ruQ8Tx46wSMktKV3J
 LRWhnLTA


 Thanks
 Zhi Chang

 -- Original --
 *From: * "Abhilash Goyal";
 *Date: * Mon, Aug 29, 2016 05:18 PM
 *To: * "openstack-dev";
 *Subject: * [openstack-dev] tacker vnf-create is not bringing up all
 theinterfaces

 [Tacker]
 Hello team,
 I am trying to make an OpenWRT VNF through tacker using this vnf-d
 .
 VNF is spawning successfully, but expected VNF should have 3 connecting
 points with first one in management network, but this is not happening. It
 is getting up with default network configuration because of this, IPs are
 not getting assigned to it automatically.
 Guidance would be appreciated.

 --
 Abhilash Goyal


 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>>
>>> --
>>> Abhilash Goyal
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Abhilash Goyal
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Proposing Yong Sheng Gong for Tacker core team

[Sridhar Ramaswamy]

We have enough votes to proceed.

Yong - welcome to the Tacker core team!

- Sridhar

On Tue, Aug 23, 2016 at 12:06 PM, Stephen Wong <stephen.kf.w...@gmail.com>
wrote:

> +1
>
> On Tue, Aug 23, 2016 at 8:55 AM, Sridhar Ramaswamy <sric...@gmail.com>
> wrote:
>
>> Tackers,
>>
>> I'd like to propose Yong Sheng Gong to join the Tacker core team. Yong is
>> a seasoned OpenStacker and has been contributing to Tacker project since
>> Nov 2015 (early Mitaka). He has been the major force in helping Tacker to
>> shed its *Neutronisms*. He has low tolerance on unevenness in the code
>> base and he fixes them as he goes. Yong also participated in the Enhanced
>> Placement Awareness (EPA) blueprint in the Mitaka cycle. For Newton he took
>> up himself cleaning up the DB schema and in numerous reviews to keep the
>> project going. He has been a dependable member of the Tacker community [1].
>>
>> Please chime in with your +1 / -1 votes.
>>
>> thanks,
>> Sridhar
>>
>> [1] http://stackalytics.com/report/contribution/tacker/90
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Proposing Yong Sheng Gong for Tacker core team

[Sridhar Ramaswamy]

 Tackers,

I'd like to propose Yong Sheng Gong to join the Tacker core team. Yong is a
seasoned OpenStacker and has been contributing to Tacker project since Nov
2015 (early Mitaka). He has been the major force in helping Tacker to shed
its *Neutronisms*. He has low tolerance on unevenness in the code base and
he fixes them as he goes. Yong also participated in the Enhanced Placement
Awareness (EPA) blueprint in the Mitaka cycle. For Newton he took up
himself cleaning up the DB schema and in numerous reviews to keep the
project going. He has been a dependable member of the Tacker community [1].

Please chime in with your +1 / -1 votes.

thanks,
Sridhar

[1] http://stackalytics.com/report/contribution/tacker/90
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] infra_driver and mgmt_driver

[Sridhar Ramaswamy]

Hi Yong Sheng,

Sorry, missed this email from earlier.

Yes, absolutely. We should deprecate both of them in Newton and remove
it from the API in Ocata.

thanks,
Sridhar

On Tue, Aug 9, 2016 at 8:39 PM, gong_ys2004  wrote:
> Hi Sridhar,
>
> You said in https://review.openstack.org/#/c/255146/ we should not expose
> the infra_driver and mgmt_driver to user,
> but they have been already exposed by API at
> https://github.com/openstack/tacker/blob/master/tacker/extensions/vnfm.py#L205,
>
> so what do you think?
> Do we need remove the infra_driver and mgmt_driver from API side?
>
> I think we can remove these two drivers since all of them are indicated by
> VIM.
>
> Regards,
> yong sheng gong

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Weekly meeting agenda

[Sridhar Ramaswamy]

Hi Dharmendra,

Sure, will add it to the agenda. However keep in mind, Newton release
related items are higher priority though.

- Sridhar

On Mon, Aug 8, 2016 at 5:55 AM, Dharmendra Kushwaha
<dharmendra.kushw...@nectechnologies.in> wrote:
> Dear Sridhar,
>
> Can we also discuss the NSD?
>
> Thanks & Regards
> Dharmendra Kushwaha
> ________
> From: Sridhar Ramaswamy [sric...@gmail.com]
> Sent: Monday, August 08, 2016 8:49 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [tacker] Weekly meeting agenda
>
> Tackers,
>
> Here is the agenda for this week's irc meeting,
>
> https://wiki.openstack.org/wiki/Meetings/Tacker
>
> - Announcements
> - Newton release deadlines
> - Newton priorities - feature / RFE go/no-go check
> - Mistral workflow BP
> - Open Discussion
>
> Let me know if you've anything else to discuss.
>
> thanks,
> Sridhar
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Weekly meeting agenda

[Sridhar Ramaswamy]

Tackers,

Here is the agenda for this week's irc meeting,

https://wiki.openstack.org/wiki/Meetings/Tacker

- Announcements
- Newton release deadlines
- Newton priorities - feature / RFE go/no-go check
- Mistral workflow BP
- Open Discussion

Let me know if you've anything else to discuss.

thanks,
Sridhar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Weekly meeting Aug, 2, 2016 cancelled

[Sridhar Ramaswamy]

Tackers,

Since we just met last Wed & Thurs for our midcycle meetup and, there
is no solid agenda item, I'm cancelling tomorrow's Tacker weekly
meeting.

Please use the extra time to continue to review and push patchsets for
Newton features like,

VNF-FFG
VNF Scaling
Event Audit Support
Alarm Monitoring

Of course, if you have any questions please reach out in #tacker channel.

thanks,
Sridhar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Midcycle Meetup Agenda - Final

[Sridhar Ramaswamy]

Tacker,

https://etherpad.openstack.org/p/tacker-newton-midcycle

Please find below the final agenda for the two day midcycle meetup.
Looking forward for some interesting discussions.

Agenda
==

Wed July 27


13:00 - 13:15 - Intro, agenda bashing
13:15 - 14:00 - VNFC (tbh and manikanta)
14:00 - 14:45 - State & Future of Scaling and Monitoring (Kanagaraj
and tung_doan)
14:45 - 15:00 - Break
15:00 - 15:45 - Multi-Tenancy support (sripriya)
15:45 - 16:30 - VNF status evolution (sridhar_ram, kanagaraj)
16:30 - 17:15 - State & Future of VNF Forwarding Graph & SFC  (Tim
Rozet & Stephen Wong)
17:15 - 18:00 - Wrap up day 1, Prep for Day 2

Thursday July 28
---

13:00 - 13:15 - Roll call + Recap of Day 1
13:15 - 14:00 - Network Services Descriptor (dkushwaha & tbh
14:00 - 14:45 - Mistral Integration
14:45 - 15:00 - NFVO and VNFM separation (sridhar_ram
15:00 - 15:45 - Glare integration (NFV Catalog)
15:45 - 16:30 - State of Tacker Refactoring (sripriya)
16:30 - 17:15 - Open Discussion - Governance, Meeting time, Review cadence
17:15 - 18:00 - Wrap up

- Sridhar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Mascot for Tacker

[Sridhar Ramaswamy]

Based on the inputs so far, we will go ahead with Squid for Tacker!

- Sridhar

On Mon, Jul 18, 2016 at 1:48 PM, Sridhar Ramaswamy <sric...@gmail.com> wrote:
> Tackers:
>
> Please provide your inputs to select a Mascot for Tacker in the
> etherpad. This is based on the recent initiative from OpenStack
> marketing team, see http://www.openstack.org/project-mascots for more
> details. There is already an exciting logo proposal in the etherpad
> below :)
>
> https://etherpad.openstack.org/p/tacker-mascot

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] No weekly meeting next week - July 26th, 2016

[Sridhar Ramaswamy]

As we are hosting our newton midcycle meetup next week [1], I'm
cancelling our regular weekly irc meeting. Please continue to reach
out to the team in #tacker IRC to flag any issues / reviews.

- Sridhar

[1] https://etherpad.openstack.org/p/tacker-newton-midcycle

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Glance][Heat][Murano][App-Catalog][Tacker] Glare is ready for wider review

[Sridhar Ramaswamy]

This is great! This is something we have penciled in to take up for Tacker.

We would love to start collaborating with your team to explore ways to
store various Tacker  (TOSCA) templates like VNFD, FFGD, NSD, etc in
Glare instead of in Tacker db tables. We have an agenda item on this
in our upcoming midcycle meetup [1]. It will be great if you can join
that session to help us kick start this effort.

- Sridhar

[1] https://etherpad.openstack.org/p/tacker-newton-midcycle

On Tue, Jul 19, 2016 at 4:31 AM, Mikhail Fedosin  wrote:
> Hello! Today I'm happy to announce that Glare's code is done and the service
> is ready for review [1].
>
> Glare (from GLance Artifact REpository) is a new service in the Glance
> project that provides a secure and customizable unified binary repository
> for OpenStack [2].
>
> The idea behind Glare is to allow various OpenStack services to catalog
> different binary objects they use to operate. Images used by Nova to run the
> VMs are just the best known examples of such objects; other examples include
> Heat templates, Tacker blueprints, Murano packages, and so on. Obviously,
> this functionality is common for different kinds of objects, and is usually
> unrelated to the primary mission of respective projects using these objects.
> That's why we implemented a dedicated service that will take care of
> managing various data assets in OpenStack clouds.
>
> This service fills a vacant niche in OpenStack and is intended to become a
> unified catalog of structured meta-information, as well as related binary
> data (with these objects comprising the 'artifacts'). In general Glare
> provides next key functionality, it:
>   * stores the objects reliably;
>   * guarantees their immutability once they're stored;
>   * provides search capabilities to find objects in the catalog;
>   * controls access to the objects by enforcing usage and modification
> policies, sharing and publication scenarios and so on;
>   * returns the detailed info about the requested objects;
>   * enables fetching of objects and manages their lifecycle;
>   * supports import/export the objects between clouds.
>
> Our next steps are related to help integrate various projects with Glare and
> implement artifact types for them [3]. Currently we are working with Heat,
> Murano and App-Catalog teams, but if you have any binary assets you want to
> catalog reliably - feel free to contact me and we will help your project to
> get the same functionality like Nova gets from Glance.
>
> Links:
> [1] Glare's code top commit: https://review.openstack.org/#/c/330459/5
> [2] Merged Glare API spec: https://review.openstack.org/#/c/283136/
> [3] Prototype of Heat artifact type:
> https://review.openstack.org/#/c/292327/46/glance/objects/heat-templates.py
>
> Best regards.
> Mikhail Fedosin
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Mascot for Tacker

[Sridhar Ramaswamy]

Tackers:

Please provide your inputs to select a Mascot for Tacker in the
etherpad. This is based on the recent initiative from OpenStack
marketing team, see http://www.openstack.org/project-mascots for more
details. There is already an exciting logo proposal in the etherpad
below :)

https://etherpad.openstack.org/p/tacker-mascot

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nfv][tacker] Virtual Midcycle Meetup - Mark you calendars

[Sridhar Ramaswamy]

As finalized in the recent weekly meeting [1], Tacker Virtual Midcycle
Meetup is planned for July 27 & 28th. The meetup is spread over two days,
5-hours each day with a time slot that tries to spread the pain evenly :)

Here is the event etherpad,

https://etherpad.openstack.org/p/tacker-newton-midcycle

Please RSVP in the pad and add your topics of interest.

thanks,
Sridhar

[1]
http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-07-05-16.00.log.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Weekly meeting agenda - July 5, 2016

[Sridhar Ramaswamy]

https://wiki.openstack.org/wiki/Meetings/Tacker

1600 UTC Tuesday @ #openstack-meeting

   - Announcements
   - Audit Event Log - https://review.openstack.org/321370
   - Network Services Descriptor (NSD) - https://review.openstack.org/304667
   - Grooming Midcycle Meetup topics -

 - https://etherpad.openstack.org/p/tacker-newton-midcycle


   - Open Discussion
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nfv][tacker] Weekly Meeting Agenda - Jun 27, 2016

[Sridhar Ramaswamy]

We are resuming the meeting after last week's break due to OPNFV Summit.

When: 1600 UTC Tuesday

Where: #openstack-meeting

Here is the proposed agenda [1]

   - Announcements
   - Updates from OPNFV Summit
   - VNF-FFG --> VNFM --> networking-sfc interaction
   - Grooming Midcycle Meetup topics
   - Open Discussion


Please chime in if you've anything else to discuss.

[1] https://wiki.openstack.org/wiki/Meetings/Tacker
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

[Sridhar Ramaswamy]

Thanks for the responses, I'm closing the vote.

Kanagaraj - welcome to the Tacker core team!

On Sun, Jun 19, 2016 at 7:25 PM, bharath thiruveedula <
bharath_...@hotmail.com> wrote:

> +1
> --
> To: openstack-dev@lists.openstack.org
> From: bob.haddle...@nokia.com
> Date: Fri, 17 Jun 2016 12:12:13 -0500
>
> Subject: Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to
> Tacker core team
>
> +1.  Kanagaraj will be a great addition to the team.
>
> Bob
>
> On 6/16/2016 1:45 PM, Karthik Natarajan wrote:
>
> +1. Thanks Kanagaraj for making such a great impact during the Newton
> cycle.
>
>
>
> *From:* Sripriya Seetharam [mailto:ssee...@brocade.com
> <ssee...@brocade.com>]
> *Sent:* Thursday, June 16, 2016 10:35 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org> <openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to
> Tacker core team
>
>
>
> +1
>
>
>
>
>
> -Sripriya
>
>
>
>
>
> *From:* Sridhar Ramaswamy [mailto:sric...@gmail.com <sric...@gmail.com>]
> *Sent:* Wednesday, June 15, 2016 6:32 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* [openstack-dev] [tacker] Proposing Kanagaraj Manickam to
> Tacker core team
>
>
>
> Tackers,
>
> It gives me great pleasure to propose Kanagaraj Manickam to join the
> Tacker core team. In a short time, Kanagaraj has grown into a key member of
> the Tacker team. His enthusiasm and dedication to get Tacker code base on
> par with other leading OpenStack projects is very much appreciated. He is
> already working on two important specs in Newton cycle and many more fixes
> and RFEs [1]. Kanagaraj is also a core member in the Heat project and this
> lends well as we heavily use Heat for many Tacker features.
>
> Please provide your +1/-1 votes.
>
> - Sridhar
>
> [1]
> http://stackalytics.com/?module=tacker-group_id=kanagaraj-manickam=marks
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__stackalytics.com_-3Fmodule-3Dtacker-2Dgroup-26user-5Fid-3Dkanagaraj-2Dmanickam-26metric-3Dmarks=CwMFaQ=IL_XqQWOjubgfqINi2jTzg=hROKXYYshyJWhFmsb7PFSLyhefOI0B-5pQmhOlAcwa8=XTvfSkjsPDJfmRDZdSXZNY1d_bJ74wj1NZaZ5zCOP6o=iQMBtQTzCUXg0nRKd1FiB3wC3ChTtDySmzqnoTSDQjU=>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions) Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker][nfv][midcycle] Straw poll on F2F vs Virtual midcycle meetup

[Sridhar Ramaswamy]

Thanks for all those who responded. The poll is closed now. It was a
unanimous pick for a Virtual midcycle meetup. I'll send out another doodle
poll to pick date & time in late July for the meetup.

- Sridhar

On Tue, Jun 7, 2016 at 5:15 PM, Sridhar Ramaswamy <sric...@gmail.com> wrote:

> Tackers,
>
> Please respond to this straw poll to gauge general interest for a midcycle
> meetup in this dev cycle,
>
> http://doodle.com/poll/2p62zzgevg6h5xkn
>
> Based on this outcome, if there is enough interest, will send another poll
> to zoom on a date (roughly 2nd half of July).
>
> thanks,
> Sridhar
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

[Sridhar Ramaswamy]

Tackers,

It gives me great pleasure to propose Kanagaraj Manickam to join the Tacker
core team. In a short time, Kanagaraj has grown into a key member of the
Tacker team. His enthusiasm and dedication to get Tacker code base on par
with other leading OpenStack projects is very much appreciated. He is
already working on two important specs in Newton cycle and many more fixes
and RFEs [1]. Kanagaraj is also a core member in the Heat project and this
lends well as we heavily use Heat for many Tacker features.

Please provide your +1/-1 votes.

- Sridhar

[1]
http://stackalytics.com/?module=tacker-group_id=kanagaraj-manickam=marks
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Cancelling weekly meeting next week (Jun 21, 2016)

[Sridhar Ramaswamy]

I'll be away next week attending OPNFV Summit. Hence cancelling Tacker irc
meeting on Jun 21st. We will resume the week after - on Tuesday Jun 28th,

https://wiki.openstack.org/wiki/Meetings/Tacker

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nfv][tacker] Tacker sessions @ OPNFV Summit, Berlin

[Sridhar Ramaswamy]

For the folks going to OPNFV Summit @ Berlin next week, and interested in
NFV Orchestration + OpenStack, please consider stopping by at the following
OpenStack Tacker related sessions,

1) OPNFV Design Summit - Day 1/June 20th,
 https://wiki.opnfv.org/display/EVNT/Berlin+Design+Summit+Planning

2) OpenStack Tacker - Open Platform for NFV Orchestration - Thursday June
23 @ 3:30pm

thanks,
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet] [tacker] Request to create puppet-tacker

[Sridhar Ramaswamy]

This is exciting. Thanks Dan for your contribution!

I hope to see a similar contribution for Tacker deployment using
openstack-ansible :)

- Sridhar

On Wed, Jun 8, 2016 at 8:18 AM, Dan Radez  wrote:

> FYI, tacker community:
> https://review.openstack.org/#/c/327173/
> https://review.openstack.org/#/c/327178/
>
> Radez
>
> On 06/08/2016 10:54 AM, Dan Radez wrote:
> > sure will, thx Emilien
> > Dan
> >
> > On 06/08/2016 09:08 AM, Emilien Macchi wrote:
> >> Yeah, super good news!
> >> Please do the same as I did in https://review.openstack.org/326720 and
> >> https://review.openstack.org/326721
> >>
> >> Add me as reviewer because I need to sign-off the 2 patches (I'm
> current PTL).
> >> Once it's done & merged, you'll be able to deprecate the old
> >> repository on your github with a nice README giving the link of the
> >> new module.
> >>
> >> I haven't looked at the code yet but we'll probably have to adjust
> >> some bits, add some testing (beaker [1], etc). Please make sure that
> >> we have some packaging available in RDO (I checked on Ubuntu and they
> >> don't provide it) so we can download it during our beaker tests.
> >>
> >> Also a last thing, in order to help us to make the module compliant &
> >> consistent, please read how we wrote the recent modules. For example
> >> you can look puppet-gnocchi or puppet-aodh that are clean modules.
> >> We recently had a lot of new modules: vitrage, watcher, tacker,
> >> congress, (I'm working now on octavia) - which means reviews might
> >> take more time than usual because our team will review the new modules
> >> carefuly to make sure the code is clean & consistent from beginning
> >> (and avoid the puppet-monasca story). Please be patient and help us by
> >> reading how we did other modules.
> >>
> >> Thanks a ton for your collaboration and we're looking forward for this
> >> new challenge,
> >>
> >> [1] https://github.com/puppetlabs/beaker
> >>
> >> On Wed, Jun 8, 2016 at 8:11 AM, Iury Gregory 
> wrote:
> >>> Awesome!
> >>>
> >>> You just need to follow the same process that Emilien pointed for
> >>> puppet-congress. If you need any help please let us know.
> >>>
> >>> 1- Move  https://github.com/radez/puppet-tacker to OpenStack
> >>> 2- Add it to our governance
> >>> 3- Follow
> >>>
> http://docs.openstack.org/developer/puppet-openstack-guide/new-module.html
> >>>
> >>>
> >>>
> >>> 2016-06-08 8:56 GMT-03:00 Dan Radez :
> 
>  I also have puppet-tacker module that has existed before the project
> was
>  part of big tent.
> 
>  It was based on cookie cutter originally but will probably need some
>  adjustments to adhere to standards.
> 
>  I'd like to get the project establish so that the code can be run
>  through the proper review process.
> 
>  exiting repo is here: https://github.com/radez/puppet-tacker
> 
>  Dan Radez
>  freenode: radez
> 
> 
> __
>  OpenStack Development Mailing List (not for usage questions)
>  Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> ~
> >>> Att[]'s
> >>> Iury Gregory Melo Ferreira
> >>> Master student in Computer Science at UFCG
> >>> E-mail:  iurygreg...@gmail.com
> >>> ~
> >>>
> >>>
> __
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>
> >>
> >>
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker][nfv][midcycle] Straw poll on F2F vs Virtual midcycle meetup

[Sridhar Ramaswamy]

Tackers,

Please respond to this straw poll to gauge general interest for a midcycle
meetup in this dev cycle,

http://doodle.com/poll/2p62zzgevg6h5xkn

Based on this outcome, if there is enough interest, will send another poll
to zoom on a date (roughly 2nd half of July).

thanks,
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Proposing Bharath Thiruveedula to Tacker core team

[Sridhar Ramaswamy]

Closing the vote, as all existing core members voted.

Bharath - Welcome to the Tacker core team!

On Mon, Jun 6, 2016 at 11:39 AM, Stephen Wong <stephen.kf.w...@gmail.com>
wrote:

> +1
>
> On Fri, Jun 3, 2016 at 9:23 PM, Haddleton, Bob (Nokia - US) <
> bob.haddle...@nokia.com> wrote:
>
>> +1
>>
>> Bob
>>
>> On Jun 3, 2016, at 8:24 PM, Sridhar Ramaswamy <sric...@gmail.com> wrote:
>>
>> Tackers,
>>
>> I'm happy to propose Bharath Thiruveedula (IRC: tbh) to join the tacker
>> core team. Bharath has been contributing to Tacker from the Liberty cycle,
>> and he has grown into a key member of this project. His contribution has
>> steadily increased as he picked up bigger pieces to deliver [1].
>> Specifically, he contributed the automatic resource creation blueprint [2]
>> in the Mitaka release. Plus tons of other RFEs and bug fixes [3]. Bharath
>> is also a key contributor in tosca-parser and heat-translator projects
>> which is an added plus.
>>
>> Please provide your +1/-1 votes.
>>
>> Thanks Bharath for your contributions so far and much more to come !!
>>
>> [1]
>> http://stackalytics.com/?project_type=openstack=all=commits_id=bharath-ves=tacker-group
>> [2]
>> https://blueprints.launchpad.net/tacker/+spec/automatic-resource-creation
>> [3] https://bugs.launchpad.net/bugs/+bugs?field.assignee=bharath-ves
>> <https://bugs.launchpad.net/bugs/+bugs?field.searchtext=%3Alist=NEW%3Alist=OPINION%3Alist=INVALID%3Alist=WONTFIX%3Alist=EXPIRED%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED%3Alist=FIXRELEASED%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE_option=any=bharath-ves_reporter=_commenter===_combinator=ALL_upstream-empty-marker=1_cve.used=_dupes.used=_dupes=on_me.used=_patch.used=_branches.used=_branches=on_no_branches.used=_no_branches=on_blueprints.used=_blueprints=on_no_blueprints.used=_no_blueprints=on=Search=-targetname=0>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org
>> ?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Proposing Bharath Thiruveedula to Tacker core team

[Sridhar Ramaswamy]

Tackers,

I'm happy to propose Bharath Thiruveedula (IRC: tbh) to join the tacker
core team. Bharath has been contributing to Tacker from the Liberty cycle,
and he has grown into a key member of this project. His contribution has
steadily increased as he picked up bigger pieces to deliver [1].
Specifically, he contributed the automatic resource creation blueprint [2]
in the Mitaka release. Plus tons of other RFEs and bug fixes [3]. Bharath
is also a key contributor in tosca-parser and heat-translator projects
which is an added plus.

Please provide your +1/-1 votes.

Thanks Bharath for your contributions so far and much more to come !!

[1]
http://stackalytics.com/?project_type=openstack=all=commits_id=bharath-ves=tacker-group
[2]
https://blueprints.launchpad.net/tacker/+spec/automatic-resource-creation
[3] https://bugs.launchpad.net/bugs/+bugs?field.assignee=bharath-ves

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Proposing Lin Cheng for tacker-horizon core team

[Sridhar Ramaswamy]

I think we have enough votes to proceed...

Lin,

Welcome to Tacker Horizon core team!

- Sridhar

On Thu, May 26, 2016 at 9:13 PM, Janki Chhatbar <jankih...@gmail.com> wrote:

> +1
>
> Thanking you
> Janki Chhatbar
> OpenStack | SDN | Docker
> simplyexplainedblog.wordpress.com
> On May 26, 2016 11:16 PM, "Sridhar Ramaswamy" <sric...@gmail.com> wrote:
>
>> Tackers,
>>
>> I'd like to propose Lin Cheng to join as a tacker-horizon core team
>> member. Lin has been our go-to person for all guidance related to UI
>> enhancements for Tacker. He has been actively reviewing patchsets in
>> this area [1] and also contributed to setup the unit test framework for
>> tacker-horizon repo.
>>
>> Please provide your +1/-1 votes.
>>
>> - Sridhar
>>
>> [1]
>> http://stackalytics.com/?project_type=all=marks=all=tacker-group_id=lin-hua-cheng
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Proposing Lin Cheng for tacker-horizon core team

[Sridhar Ramaswamy]

Tackers,

I'd like to propose Lin Cheng to join as a tacker-horizon core team member.
Lin has been our go-to person for all guidance related to UI enhancements
for Tacker. He has been actively reviewing patchsets in this area [1] and
also contributed to setup the unit test framework for tacker-horizon repo.

Please provide your +1/-1 votes.

- Sridhar

[1]
http://stackalytics.com/?project_type=all=marks=all=tacker-group_id=lin-hua-cheng
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Cancelling Tacker weekly IRC meeting on Tuesday 05/24

[Sridhar Ramaswamy]

Please continue to get the spec reviews going and reach out in #tacker
channel to flag any issues.

- Sridhar

On Mon, May 23, 2016 at 2:01 PM, Sridhar Ramaswamy <sric...@gmail.com>
wrote:

> Tackers -
>
> Does anyone have a specific agenda item for tomorrow's IRC weekly meeting?
> I know many specs are in flight and reviews are happening in gerrit. If I
> don't hear any specific topics to discuss by 10:00 UTC I'll cancel the
> meeting and give an hour back.
>
> - Sridhar
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] any agenda item for tomorrow's IRC meeting ?

[Sridhar Ramaswamy]

Tackers -

Does anyone have a specific agenda item for tomorrow's IRC weekly meeting?
I know many specs are in flight and reviews are happening in gerrit. If I
don't hear any specific topics to discuss by 10:00 UTC I'll cancel the
meeting and give an hour back.

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Agenda for weekly IRC meeting

[Sridhar Ramaswamy]

Tackers,

This week's meeting will be wholly focused on alarm based monitoring and
auto-scaling work.

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_May_17.2C_2016

1600 UTC Tuesday

   - Announcements
   - Alarm based VDU Monitoring & Scaling
  - User Scenarios
  - Scope - what it is and what it isn't
  - Options
  - Conclusion
   - Open Discussion


thanks,
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][NFV] Tacker - Weekly IRC Meeting - new time

[Sridhar Ramaswamy]

Tackers,

We are resuming Tacker IRC weekly meeting at a new time slot (an hour
earlier) and at a new channel.

When: Tuesday 1600 UTC
Where: #openstack-meeting
Duration: 1hr

Here is the agenda for tomorrow's meeting,


https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_May_10.2C_2016


   - Announcements
   - Newton Working Plan
   - Alarm based VDU Scaling - Scope, What it is and What it isn't
   - VNF FFG - Descriptor Template
   - Open Discussion


Let's pick up steam for Newton!
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] No IRC weekly meeting this week

[Sridhar Ramaswamy]

Tackers -

Heads up. As decided in last meeting [1] we are skipping the weekly meeting
this week on Tuesday, May 3rd. We will resume the meeting starting next
week. There was a request in the design summit to move the meeting one hour
ahead to compensate for the daylight savings time. I'll send an update in
the next few days with the meeting details (specifically the channel).

[1]
http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-04-19-17.01.log.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [opnfv-tech-discuss][NFV] BoF on NFV Orchestration

[Sridhar Ramaswamy]

Greetings,

I'm soliciting inputs, and if interested in this topic, your presence for
the upcoming BoF session on NFV Orchestration during the Austin summit,

https://www.openstack.org/summit/austin-2016/summit-schedule/events/8468

We had a packed session for a similar event in the Tokyo summit with many
great inputs shared on this topic. I've created an etherpad with few
cross-organizational topics to get the discussion going,


https://etherpad.openstack.org/p/austin-2016-nfv-orchestration-bof

Please share your thoughts, either here in the ML or etherpad to make this
event a success.

thanks,
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Refactoring heat-driver

[Sridhar Ramaswamy]

Now that Mitaka release is out, this is a good time to consider refactoring
Tacker's heat-driver. This driver was one of the big module we inherited
but it got even bloated with recent enhancements.

I've captured some ideas on how to shuffle things out of this component in
the etherpad [1]. Thoughts ?

- Sridhar

[1] https://etherpad.openstack.org/p/tacker-newton-heatdriver-refactoring
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Agenda for weekly meeting - Mar 29, 2016

[Sridhar Ramaswamy]

Here is the agenda for tomorrow's tacker meeting.

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Mar_29.2C_2016

1700 UTC Tuesday / #openstack-meeting-4

   - Announcements
   - Mitaka Release Review
   - Mitaka bugs / blockers
   - Mitaka Docs -
   http://docs.openstack.org/contributor-guide/quickstart/new-projects.html
   - Newton Summit Planning
   - Open Discussion
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] No IRC meeting this week

[Sridhar Ramaswamy]

As I didn't get any volunteers [1] to run the irc meeting I'm cancelling it
for this week. We will resume the week after on Mar 29th, 2016.

Hope this will give an hour back to the community towards their time to
wrap up last minute Mitaka targets. Please keep you response times tight
for those reviews. If you've have any questions on Mitaka related issues
please reached out at #tacker channel.

- Sridhar

[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-March/089718.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Any volunteers to run next IRC weekly meeting ?

[Sridhar Ramaswamy]

I'm out on a day long offsite next Tuesday and won't be able to run our
weekly irc meeting. Any volunteers to pick it up for next week?

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Agenda for weekly meeting - Mar 15th

[Sridhar Ramaswamy]

Here is the agenda for tomorrow's weekly meeting,

1700 UTC Tuesday

irc #: openstack-meeting-4

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Mar_15.2C_2016

   - Announcements
   - Mitaka status
  - TOSCA parser and dependent features (auto-resource creation & EPA)
  - MultiSite
   - Mitaka bugs
   - Newton series: Network Service Descriptor support
  -
  
https://docs.google.com/presentation/d/1prnTLewkX3Dd2OYDSrEHgbq9RUSOj8ql8w3Sb3wcms8/edit
   - Open Discussions
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] PTL Candidacy

[Sridhar Ramaswamy]

My name is Sridhar Ramaswamy and I'd like to announce my candidacy as
Tacker PTL for the upcoming Newton cycle.

Tacker is a newly minted big-tent project. I was involved in Tacker
right from the days when it used to be a Neutron ServiceVM project and
during its transition to the NFV Orchestration use case. I was leading
the project in an informal PTL role over the last two cycles. We had
the goal of getting into the big tent in Mitaka and few weeks back we
successfully got accepted - woot! Credit goes to the amazing community
that believed in Tacker and taken it this far.

Mitaka cycle was a quite packed. We are landing many features -
TOSCA-parser integration, MultiSite VNF placement, Enhanced VNF
placement (using Nova NFV smarts) and automatic resource creation. We
also did tons of code clean up to detach Tacker from its original
Neutron roots. Beyond all this I'm really proud of growing the team
that is quite diverse for an early stage project [1]. We also
increased our core team size in Mitaka.

Still we have lot more to do in front of us and if elected I'll work
towards the following goals for Newton:

Features: NFV Orchestration is a broad space. We have a lot to build.
However, we got to pace ourselves as we go through this journey. We
have many interesting features in the radar like Network Services
Descriptor (NSD) to orchestrate a sequence of VNFs to stand up a
network service and VNF Scaling - another highly sought out feature.
I also support the recent decision to use networking-sfc APIs for
Tacker VNF Forwarding Graph. I'm confident we would be able to land
this in Newton.

Technical Debt: We did lots of code cleanup over Mitaka cycle. Still
we mostly focused on getting new features. In the Newton cycle, we
need to increase our investment in refactoring the aging code that we
forked off from Neutron. Some of the possible refactorings in our
sights are in wsgi layer (pecan), in APIs (micro-versioning) and heat
driver modularity. Decomposing Tacker server into subcomponents is a
stretch goal which we should get started in the Newton cycle.

Release sanity:  Now that we are under big tent we need to adhere to
proper cycle deadlines and milestones. We are learning quickly the
knobs in the area of release management. I'll work towards getting
our release pipeline in order in Newton.

Gate test: We have a decent amount of gate tests. However, we need to
keep adding more. I'll work towards increasing the number of gate
tests particularly using VNFs like OpenWRT.

Community: Growing the community is one of the top goals in Newton. We
need to increase our core team as well. As always I'll do my best to
welcome new community members, vendors, and operators to join Tacker.

Overall we need to balance out our investments between new features
and technical debt / project stabilization in Newton.

Thanks for your consideration.
- Sridhar
IRC: sridhar_ram

[1] http://stackalytics.com/?release=all=tacker-group=patches
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Branch miss-match between server and client in Kilo

[Sridhar Ramaswamy]

Hi Janki,

Thanks for reporting this issue and it is a valid one. However we need to
fix up our gate tests to skip doc8 test for stable/kilo to merge your
patchset. Given Kilo is close to EOL (end-of-life) would you mind switching
over to use stable/liberty ? For Tacker, Kilo was one of the early release
and we came a long way "cleaning up" the project over Liberty and Mitaka
(which is wrapping up). Again, if you are particular about Kilo for any
specific reason, let us know. We will find a way to work it out.

BTW, I see you are new to OpenStack contributions - a warm welcome! We have
many interesting work items that you could take up, see [1], particularly
the ones with low-hanging-fruit tag. Stop by #tacker channel if you need
help picking one.

- Sridhar

[1] https://goo.gl/S3FAOk


On Wed, Mar 9, 2016 at 8:16 PM, Janki Chhatbar 
wrote:

> Hi All
>
> Greetings for the day!
>
> I have noticed that while installing* OpenStack Kilo* using DevStack, the
> server components cloned are stable/kilo whereas the client components
> cloned are master. This leads to errors in installation or commands
> miss-match. For eg.
>
> *In tacker,*
> tacker git repo is stable/kilo which points to incorrect git repo URL. I
> have filled a  bug and proposed a patch for this (
> https://bugs.launchpad.net/tacker/+bug/1555130)
>
> *In Magnum*,
> *magnum stable/kilo* clones *python-magnumclient master* which leads to
> command mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).
>
>
>1. Does this affect all other services?
>2. Does this mean that the branch needs to be changed for all the
>service's clients? The change will be in /devstack/lib/{service} file in
>"GITBRANCH" variable.
>
>  If changes are required, I am willing to work on those.
>
> Thanking you
>
> Janki Chhatbar
> OpenStack | SDN | Docker
> (+91) 9409239106
> simplyexplainedblog.wordpress.com
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Weekly meeting agenda - Mar 1, 2016

[Sridhar Ramaswamy]

Here is the agenda for this week's weekly meeting,

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Mar_1.2C_2016

1700 UTC Tuesday
#openstack-meeting-4

* Announcements
* TOSCA parser integration
** Basic parser integration
** Auto Resource Creation
** Enhanced VNF placement
* Mitaka fit and finish - RFEs and Bugs
* Open Discussion
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker][networking-sfc] Tacker VNFFG - SFC integration updates

[Sridhar Ramaswamy]

On Wed, Feb 17, 2016 at 11:23 AM, Russell Bryant <rbry...@redhat.com> wrote:

> On 02/16/2016 02:51 PM, Sridhar Ramaswamy wrote:
> > Hi folks,
> >
> > Based on the recent discussions in [1] & [2] we are proposing to
> > rearrange our tasks related to Tacker's VNFFG component integrating with
> > the lower level SFC APIs. We now plan to integrate with networking-sfc
> > APIs first.
> >
> > Our original plan, or rather the sequence of tasks, were,
> >
> > 1) Tacker VNFFG plugin (trozet)
> > 2) Tacker VNFFG plugin --> ODL/netvirtsfc driver backend (trozet)
> > 3) Tacker VNFFG plugin --> networking-sfc driver backend (s3wong)
> > 4) networking-sfc --> ODL/netvirtsfc driver backend (TBD)
> >
> > We now propose to alter the sequence of tasks to something like this,
> >
> > 1) Tacker VNFFG plugin (trozet)
> > 2) Tacker VNFFG plugin --> networking-sfc driver backend (s3wong) -
> > /that is, introduce this as the first driver backend for Tacker VNFFG
> > instead of direct ODL/netvirtsfc driver/
> > 3) Use the code written by Tim (trozet) for Tacker's ODL/netvirtsfc
> > driver backend and help to further networking-sfc's ODL integration
> efforts.
> >
> > Quick note on (3) above, networking-sfc already has a driver for ONOS
> > SDN Controller [3]. So it should reasonably easy to bring in a ODL
> > driver for networking-sfc. This might be slightly longer than what we
> > ideally wanted for some short-term PoCs but it positions us to get the
> > eventual end goal faster.
>
> What other backends would you expect other than the networking-sfc
> backend?  Is it none for now, but just leaving it open for an
> alternative Neutron API should one come up?
>

Yep, there is no other backends planned beyond networking-sfc. In fact I
happy that most things in our sight (for Tacker) like ODL, ONOS and OVN are
already under consideration in the networking-sfc project. Still it will be
good keep the layers separate - the top-half with forwarding-graph related
stuff and the bottom half handling the calls to low-level sfc api.

- Sridhar


>
> --
> Russell Bryant
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker][networking-sfc] Tacker VNFFG - SFC integration updates

[Sridhar Ramaswamy]

Hi folks,

Based on the recent discussions in [1] & [2] we are proposing to rearrange
our tasks related to Tacker's VNFFG component integrating with the lower
level SFC APIs. We now plan to integrate with networking-sfc APIs first.

Our original plan, or rather the sequence of tasks, were,

1) Tacker VNFFG plugin (trozet)
2) Tacker VNFFG plugin --> ODL/netvirtsfc driver backend (trozet)
3) Tacker VNFFG plugin --> networking-sfc driver backend (s3wong)
4) networking-sfc --> ODL/netvirtsfc driver backend (TBD)

We now propose to alter the sequence of tasks to something like this,

1) Tacker VNFFG plugin (trozet)
2) Tacker VNFFG plugin --> networking-sfc driver backend (s3wong) - *that
is, introduce this as the first driver backend for Tacker VNFFG instead of
direct ODL/netvirtsfc driver*
3) Use the code written by Tim (trozet) for Tacker's ODL/netvirtsfc driver
backend and help to further networking-sfc's ODL integration efforts.

Quick note on (3) above, networking-sfc already has a driver for ONOS SDN
Controller [3]. So it should reasonably easy to bring in a ODL driver for
networking-sfc. This might be slightly longer than what we ideally wanted
for some short-term PoCs but it positions us to get the eventual end goal
faster.

Comments, suggestions welcome!

thanks,
Sridhar

[1] https://review.openstack.org/#/c/276417
[2]
http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-02-16-17.00.log.html
[3]
https://github.com/openstack/networking-onos/blob/master/networking_onos/services/sfc/driver.py
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Agenda for weekly meeting - Feb 9, 2016

[Sridhar Ramaswamy]

Here is the agenda for tomorrow's IRC meeting.

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Feb_9.2C_2016

1700 UTC Tuesday

   - Announcements
   - TOSCA parser integration - https://review.openstack.org/#/c/275475/
   - Mitaka Release Deadline -
   http://releases.openstack.org/mitaka/schedule.html
   - RFEs up for grabs -
   https://bugs.launchpad.net/tacker/+bugs?field.tag=mitaka-rfe
   - Open Discussion
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker][tacker] TOSCA-Parser 0.4.0 PyPI release

[Sridhar Ramaswamy]

Thanks for the note Sahdev. Appreciate your support in getting in TOSCA NFV
Profile quickly in time for our Mitaka plans.

This is awesome collaboration between tacker and heat-translator projects.
Lets keep this going!

- Sridhar

PS: fixed the subject :)

On Wed, Feb 3, 2016 at 6:08 PM, Sahdev P Zala  wrote:

> Hello Tacker team,
>
> Sorry I forgot to include the project name in the subject of the following
> original email, so FYI.
>
> Thanks!
>
> Regards,
> Sahdev Zala
>
> - Forwarded by Sahdev P Zala/Durham/IBM on 02/03/2016 09:03 PM -
>
> From:Sahdev P Zala/Durham/IBM@IBMUS
> To:"OpenStack Development Mailing List (not for usage questions)"
> 
> Date:02/03/2016 08:16 PM
> Subject:[openstack-dev] [tosca-parser] [heat-translator] [heat]
> TOSCA-Parser 0.4.0 PyPI release
> --
>
>
>
> Hello Everyone,
>
> On behalf of the TOSCA-Parser team, I am pleased to announce the 0.4.0
> PyPI release of tosca-parser which can be downloaded from
> *https://pypi.python.org/pypi/tosca-parser*
> 
>
> This release includes following enhancements:
>
> 1) Initial support for TOSCA Simple Profile for Network Functions
> Virtualization (NFV) v1.0
> 2) Support for TOSCA Groups and Group Type
> 3) Initial support for TOSCA Policy and Policy Types
> 4) Support for TOSCA Namespaces
> 5) Many bug fixes and minor enhancements including:
>-Fix for proper inheritance among types and custom
> relationships based on it
>-Updated min and max length with map
>-New get_property function for HOST properties similar to
> get_attribute function
>-Updated datatype_definition
>-Support for nested properties
>-Fix for incorrect inheritance in properties of
> capabilities
>-High level validation of imported template types
>-Six compatibility for urllib
>-Test updates
>  -Documentation updates
>
> Please let me know if you have any questions or comments.
>
> Thanks!
>
> Regards,
> Sahdev Zala
> PTL, Tosca-Parser
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [NFV][tacker] Notes from Tacker Midcycle Meetup

[Sridhar Ramaswamy]

Thanks for all those who participated in last week's 2-day Tacker Midcycle
meetup. It was a quite an engaging discussion! Here are the notes from the
meetup,

https://etherpad.openstack.org/p/tacker-mitaka-midcycle-notes

- Sridhar

PS: quick remainder, as we just met we are skipping our weekly IRC meeting
this week (Tuesday Feb 2nd).
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] No weekly IRC meeting next week - Feb 2

[Sridhar Ramaswamy]

Louis,

Just updated the etherpad. We planning from 9AM PST - 5PM PST.

- Sridhar

On Tue, Jan 26, 2016 at 12:35 PM, Henry Fourie <louis.fou...@huawei.com>
wrote:

> Sridhar,
>
>What time will the Tacker mid-cycle meeting start/end?
>
> -Louis
>
>
>
> *From:* Sridhar Ramaswamy [mailto:sric...@gmail.com]
> *Sent:* Tuesday, January 26, 2016 11:11 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [tacker] No weekly IRC meeting next week - Feb
> 2
>
>
>
> As discussed in today's irc meeting, we are skipping next weekly meeting
> scheduled for Tuesday Feb 2nd [1] as we already have a 2-day mid-cycle
> meetup [2] later this week.
>
>
>
> - Sridhar
>
>
>
> [1] https://wiki.openstack.org/wiki/Meetings/Tacker
>
> [2] https://etherpad.openstack.org/p/tacker-mitaka-midcycle
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] No weekly IRC meeting next week - Feb 2

[Sridhar Ramaswamy]

As discussed in today's irc meeting, we are skipping next weekly meeting
scheduled for Tuesday Feb 2nd [1] as we already have a 2-day mid-cycle
meetup [2] later this week.

- Sridhar

[1] https://wiki.openstack.org/wiki/Meetings/Tacker
[2] https://etherpad.openstack.org/p/tacker-mitaka-midcycle
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker]Automatic Resource Creation

[Sridhar Ramaswamy]

Hi Bharath,

As further discussed in today's IRC meeting [1], the image creation
proposal you laid out seems a reasonable near term approach.

It also doesn't preclude future enhancements to do image-download during
VNFD on-boarding (image pre-positiong in a multi-site scenario). In that
case VNFD in the Catalog will already have references to glance image(s) in
the target VIM and the VNF creation can directly proceed to the
instantiation phase.

On the Flavor and Network creation I would strongly suggest to stick with
Heat resources and leverage TOSCA -> HOT conversion to achieve them and not
go directly to Nova and Neutron for this purpose.

thanks,
Sridhar

[1]
http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-01-26-17.00.log.html

On Tue, Jan 26, 2016 at 6:19 AM, bharath thiruveedula <
bharath_...@hotmail.com> wrote:

> Hi Tackers,
>
> I have uploaded a new patchset for the automatic resource creation
> spec[1]. I haven't addressed some comments and as I am unable to attend to
> mitaka midcycle meetup, I am sharing below few thoughts on this spec.
>
> *Image Creation*:
>
> In the latest patchset, image creation at the time of onboarding, is the
> only reason for maintaining state for VNFD. As we discussed earlier, it may
> get difficult for the new users to understand "*state for templates?".* So
> it is better to  move image creation too on VNF creation. So if the
> template has uri, for the first VNF creation, we create the image and store
> image id for future VNF deployments. So using this option, we can provide
> parametrization of templates for images also and we can remove the
> statefulness for VNFD.
>
> *Flavor Creaton:*
>
> We can apply the same above rule in this case also. we store flavor IDs
> while deploying the first VNF and later reuse the same IDs.
>
> *Network Creation:*
>
> We can apply same rule here.
>
> Let me know your comments
>
> [1]https://review.openstack.org/#/c/250291/
>
> Regards
> Bharath T
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Reminder - Mid-cycle Meetup next week in San Jose, CA

[Sridhar Ramaswamy]

Heads up for folks interested in NFV Orchestration. Tacker team is hosting
a mid-cycle meetup next week in San Jose. Agenda, logistics and sign-up
sheet are in the etherpad [1].

- Sridhar

[1] https://etherpad.openstack.org/p/tacker-mitaka-midcycle
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Mitaka midcycle meetup - Jan 28, 29

[Sridhar Ramaswamy]

Greetings,

Tacker mid-cycle meetup is scheduled for Jan 28th & 29th in San Jose @
Brocade site.

Please update the etherpad [1] to signup and add topics of interest.

thanks,
Sridhar

[1] https://etherpad.openstack.org/p/tacker-mitaka-midcycle
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Next IRC weekly meeting - Jan 5th

[Sridhar Ramaswamy]

Tackers,

We will have our first weekly IRC meeting of 2016 this week on Tuesday Jan
5 @ UTC 1700 (our usual slot). Please find the agenda here,

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Jan_5.2C_2016

thanks,
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] No IRC weekly meetings next two weeks

[Sridhar Ramaswamy]

We are skipping the next two weekly meetings,

   - Dec 22
   - Dec 29

We will reconvene Jan 5th at our usual 1700 UTC slot.

BTW, though we skipping these meetings, tacker core team is available to
continue to review and merge patchsets over next two weeks, so keep them
coming!

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Tacker] No IRC weekly meetings next two weeks

[Sridhar Ramaswamy]

Hi Bruce,

Yes, there is enough interest to have one. Just sent a RSVP / poll for that,

http://lists.openstack.org/pipermail/openstack-dev/2015-December/082526.html

thanks,
Spider**

** - auto-correct does wonders to our name, thinking about incorporating
this into my irc nick :)


On Wed, Dec 16, 2015 at 1:22 PM, Bruce Thompson (brucet) <bru...@cisco.com>
wrote:

> Spider,
>
> Last week you talked about a face to face meeting sometime in January.
> Anything new on that?
>
> Bruce T
>
> From: Sridhar Ramaswamy <sric...@gmail.com>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Wednesday, December 16, 2015 at 2:09 PM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: [openstack-dev] [Tacker] No IRC weekly meetings next two weeks
>
> We are skipping the next two weekly meetings,
>
>- Dec 22
>- Dec 29
>
> We will reconvene Jan 5th at our usual 1700 UTC slot.
>
> BTW, though we skipping these meetings, tacker core team is available to
> continue to review and merge patchsets over next two weeks, so keep them
> coming!
>
> - Sridhar
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Mitaka midcycle meetup - RSVP / etherpad

[Sridhar Ramaswamy]

Tacker team is planning to host a 2-day mid-cycle meetup in San Jose, CA
around end of January. Please RSVP if you are interested to join with your
preferred dates in this google form,

http://goo.gl/forms/oHUfS0Q7X8

We are gathering topics in this etherpad,

https://etherpad.openstack.org/p/tacker-mitaka-midcycle

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Next IRC weekly meeting in APAC timezone

[Sridhar Ramaswamy]

Tackers,

We now have contributors from APAC region, particularly the ones
contributing to Enhanced VNF Placement area. As discussed in the last
meeting, as a one time change, the next week's IRC meeting will be held in
an APAC friendly time slot.

When: 0100 UTC Wed Dec 16th (Tue 5PM PST, Wed 9AM Beijing)

http://www.timeanddate.com/worldclock/meetingdetails.html?year=2015=12=16=1=0=0=283=64=176=33

Where: #openstack-meeting-4

Agenda:
https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_16.2C_2015_-_APAC_Timezone

Based on the participation level we can consider switching to alternate
slots in an ongoing basis.

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Tacker][Tricircle]Multi-VIM collaboration

[Sridhar Ramaswamy]

Sure.

As mentioned in the BP we stumbled into Tricycle project while researching
for this feature (and hence got mentioned in the BP). It sure looks
promising. The immediate asks from our user community is quite modest
though, so we are trying to keep the scope small. However the integration
point you mention make sense, so that Tacker + Tricircle could be one of
the deployment option. Lets continue the discussion in the gerrit as we put
all other suggestions coming in (like heat multi-cloud / multi-region) in
perspective. It will be great to get the Tacker multi-site API bake in
different multi-site deployment patterns underneath.

- Sridhar

On Tue, Dec 8, 2015 at 10:37 PM, Zhipeng Huang 
wrote:

> Hi Tacker team,
>
> As I commented in the BP[1], our team is interested in a collaboration in
> this area. I think one of the collaboration point would be to define a
> mapping between tacker multi-vim api with Tricircle resource routing api
> table [2].
>
> [1]https://review.openstack.org/#/c/249085/
> [2]
> https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#heading=h.5t71ara040n5
>
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Prooduct Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Agenda for tomorrow's IRC meeting

[Sridhar Ramaswamy]

Quick reminder on tomorrow's weekly meeting @ 1700 UTC on IRC
#openstack-meeting-4.

Here is the planned agenda,

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_8.2C_2015


   - Midcycle Meetup plans
   - Mitaka Blueprint Updates
  - Enhanced VNF Placement - adhoc IRC mtg plan
  - Multi-Site updates
  - SFC updates
  - TOSCA parser updates
   - Bugs / Docs / Open Discussion
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core

[Sridhar Ramaswamy]

Thanks everyone.

Sripriya - welcome to the tacker-core!

- Sridhar

On Wed, Nov 11, 2015 at 1:09 AM, Bharath Thiruveedula <
bharath.thiruveed...@imaginea.com> wrote:

> +1
>
> On Tue, Nov 10, 2015 at 10:42 PM, Stephen Wong <stephen.kf.w...@gmail.com>
> wrote:
>
>> +1
>>
>> On Mon, Nov 9, 2015 at 6:22 PM, Sridhar Ramaswamy <sric...@gmail.com>
>> wrote:
>>
>>> I'd like to propose Sripriya Seetharam to join the Tacker core team.
>>> Sripriya
>>> ramped up quickly in early Liberty cycle and had become an expert in the
>>> Tacker
>>> code base. Her major contributions include landing MANO API blueprint,
>>> introducing unit test framework along with the initial unit-tests and
>>> tirelessly
>>> squashing hard to resolve bugs (including chasing the recent
>>> nova-neutron goose
>>> hunt). Her reviews are solid fine tooth comb and constructive [1].
>>>
>>> I'm glad to welcome Sripriya to the core team. Current cores members,
>>> please vote
>>> with your +1 / -1.
>>>
>>> [1]
>>> http://stackalytics.com/?release=libertyuser_id=sseethaproject_type=openstack-others
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tacker] Reminder: Next IRC weekly meeting on Nov 10th Tuesday

[Sridhar Ramaswamy]

A quick reminder of the upcoming Tacker weekly meeting. Watch out, we are
switching to a new time slot and a different meeting channel,

When: Tuesday 1700 UTC
Where: IRC #openstack-meeting-4
Agenda:
   https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Nov_10.2C_2015

Feel free to add more agenda items as needed.

- Sridhar

On Tue, Nov 3, 2015 at 6:10 AM, Sridhar Ramaswamy <sric...@gmail.com> wrote:

> As discussed in the Mitaka Summit developer meetup, Tacker weekly IRC
> meeting is moved to Tuesday 1700 UTC. We are skipping this week's meeting.
> We will resume next week and mostly likely use a new meeting channel (still
> TBD for now, will announce here once confirmed).
>
> - Sridhar
>
> #sridhar_ram
> @srics
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Mitaka Priorities

[Sridhar Ramaswamy]

Here is the Mitaka Priorities etherpad, with items distilled from all those
discussions before and during the Mitaka summit.

https://etherpad.openstack.org/p/tacker-mitaka-priorities

We will discuss these items in the next weekly meeting [1]

thanks,
Sridhar

[1]
http://lists.openstack.org/pipermail/openstack-dev/2015-November/078790.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Summary from the Mitaka summit

[Sridhar Ramaswamy]

Here are the notes related to OpenStack Tacker project from Tokyo summit.

Tacker Developer Meetup
---

Rough notes are captured in the tacker design summit etherpad [1].
As discussed in the previous irc meeting [2] the team discussed
possible new irc meeting slots for the upcoming cycle. We decided
to go with Tuesday 1700 UTC slot.

Tacker - tosca-parser / heat-translator Meetup
--

Tacker developers had a meetup with tosca-parser / heat-translator
core-team members. Bob from Tacker team will pitch-in to bring
tosca-nfv profile support to tosca-parser library. He will also
co-ordinate bringing tosca-parser based template parsing to Tacker.

Birds of a Feather on NFV Orchestration using Tacker
-

We had quite a packed room full of attendees for this session.
We provided an update on what we achieved in Liberty. More
importantly, presented
the planned roadmap for Mitaka and
solicited inputs.

There was a strong support for the key features listed - Multi-VIM,
Service Function Chaining (SFC) and Platform aware VNF placement.
There were many questions on the layer of separation between VNFM
and NFVO. Some of the attendees requested the flexibility of Tacker
used just as a VNFM  or just as a NFVO. There was also a concern
whether Tacker is taking up lots of things under its scope. The
answer to this, the features added so far and the ones planned
are in response to the requests from initial adopters of Tacker.
Again, the plan is to leverage as many existing openstack projects
(like Heat) and libraries (like tosca-parser) as possible. There was
an ask to create few generic configuration-mgmt drivers like
NETCONF/YANG for quick on-boarding of VNFs.

The team will take these inputs into account in the upcoming blueprints and
RFEs.


Tacker related demos and talks,
---

1. NFV Orchestration using OpenStack Tacker / vBrownBag -
https://youtu.be/y9fYiIsIErc
2. Tacker demo orchestrating vRouter and vEPC (complex VNF) -
https://youtu.be/EfqWArz25Hg

- Sridhar

[1]  

https://etherpad.openstack.org/p/mitaka-tacker-design-summit
[2]

http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-10-22-16.09.log.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Next IRC weekly meeting on Nov 10th Tuesday

[Sridhar Ramaswamy]

As discussed in the Mitaka Summit developer meetup, Tacker weekly IRC
meeting is moved to Tuesday 1700 UTC. We are skipping this week's meeting.
We will resume next week and mostly likely use a new meeting channel (still
TBD for now, will announce here once confirmed).

- Sridhar

#sridhar_ram
@srics
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Mitaka Design Summit meetup

[Sridhar Ramaswamy]

Heads for the folks interested in Tacker. A developer meetup is planned for
Wed Oct 28th - 9:30am - 12noon. Exact location in the venue will be
finalized early next week. The following etherpad captures the current
topics to interest,

https://etherpad.openstack.org/p/mitaka-tacker-design-summit

Feel free to add as need in the etherpad.

See you all in Tokyo!
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [opentack-dev][Tacker] stable/liberty and tacker-docs

[Sridhar Ramaswamy]

Couple of things before heading to M summit,

1) stable/liberty

stable/liberty branch has been pulled. Please cherry pick relevant
fixes as needed. We will make a release after coming back from the summit.

2) Tacker docs

rst files in tacker repo are now available in readthedocs.org at
http://tacker-docs.readthedocs.org/en/latest/

On to Mitaka!

cheers,
- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team

[Sridhar Ramaswamy]

Enough time has passed.

Bob - welcome to the tacker-core team!

- Sridhar

On Thu, Oct 15, 2015 at 10:31 AM, Vishwanath Jayaraman 
wrote:

> +1
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-operators][Tacker] BoF on NFV Orchestration using Tacker

[Sridhar Ramaswamy]

Operators, Devs:

Tacker team is soliciting inputs towards building the next set of features
in the area of NFV Orchestration. We have the following Birds-of-a-Feather
session to get together on this subject,

When: Tuesday Oct 27, 2015
Where: OpenStack Tokyo Summit
Link: http://sched.co/4MZc

Some of the top roadmap items in our pipleline are,

- Forwarding Graph support using Service Function Chaining
- VNF placement across multi-VIM and other placement strategies
- Orchestrating NF across Physical, Virtual (and Containers ??)

We would love to hear your thoughts on these and possibly others. Please
feel free to forward this to other organizations of interest which could
provide inputs.

thanks!
- Tacker team
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Proposing Bob Haddleton to core team

[Sridhar Ramaswamy]

I would like to nominate Bob Haddleton to the Tacker core team.

In the current Liberty cycle Bob made significant, across the board
contributions to Tacker [1]. Starting with many usability enhancements and
squashing bugs Bob has shown commitment and consistently produced high
quality code. To cap he recently landed Tacker's health monitoring
framework to enable loadable VNF monitoring. His knowledge in NFV area is a
huge plus for Tacker as we embark onto even greater challenges in the
Mitaka cycle.

Along the lines, we are actively looking to expand Tacker's core reviewer
team. If you are interested in the NFV Orchestration / VNF Manager space
please stop by and explore Tacker project [2].

Tacker team,

Please provide your -1 / +1 votes.

- Sridhar

[1]  
http://stackalytics.com/report/users/bob-haddleton
[2]  
https://wiki.openstack.org/wiki/Tacker
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][NFV] Proposal for experimental features

[Sridhar Ramaswamy]

Folks:

We are gathering momentum in our activities towards building a VNFM / NFVO
in OpenStack Tacker project [1]. As discussed in the last week's irc
meeting [2], I'd like to propose few "experimental features" within Tacker.

It is well know practice to use experimental tag to introduce bleeding edge
features in openstack. We realize some of these experimental features have
various unknowns - sometimes in architectural clarity (e.g. specific roles
of NFVO subcomponents) and other times in specific downstream dependency
(like ODL-SFC support). The experimental feature tag will allow a safe
place to iterate in these areas, perhaps fail fast, to eventually reach our
goal. The experimental feature will be marked as such in the tacker docs
(coming soon). Once an experimental feature's usage is vetted the
"experimental" tag will be removed.

The following two features are identified as the initial candidates,

1) VNF Forwarding Graph using SFC API

SFC efforts introduced by Tim Rozet will form the basis of this track.
The wider Tacker team can pitch in to carry this forward into a functional
VNF Forwarding Graph feature.

2) Basic NSD support

 Basic Network Service Descriptor (NSD) support to instantiate a
sequence of VNFs (described in VNFD). When (1) above becomes available this
track can build on a combined NSD + VNFFD for a fully orchestrated network
service chain.

As always comments and inputs are welcome.

- Sridhar

[1]  

https://wiki.openstack.org/wiki/Tacker
[2]
http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-09-03-16.03.log.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Tacker][NFV] Heads up: switch over to master

[Sridhar Ramaswamy]

The switch over to master is now complete. Please follow the updated (and a
bit easier) Installation steps here,

https://wiki.openstack.org/wiki/Tacker/Installation


On Mon, Aug 31, 2015 at 1:32 PM, Sridhar Ramaswamy <sric...@gmail.com>
wrote:

> Tacker dev & user teams:
>
> This shouldn't be a news to folks regularly attending tacker weekly
> meetings.
>
> For others, until now Tacker code base was using stable/kilo dependencies.
> Now we will be switching over to use master based dependencies using [1]
> and [2]. We are now close to merging these two patchsets. However this will
> cause your existing devstack setups incompatible with the latest tacker
> code base. Note, before merging these patchsets a stable/kilo branch will
> be pulled.
>
> Now you've two options to continue tacker activites,
>
> 1) Switch over to use new devstack setup post merge (preferred)
> 2) If you are in middle of something and want to continue your activity
> (say a PoC in flight) consider switching tacker & python-tackerclient repo
> to stable/kilo
>
> We understand this will cause some disruption. But this is essential to
> cut over to master and get ready for the upcoming liberty release.
>
> Thanks for your support. Questions / comments welcome!
>
> - Sridhar
>
> [1] https://review.openstack.org/#/c/211403/
> [2] https://review.openstack.org/#/c/211405/
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][NFV] Heads up: switch over to master

[Sridhar Ramaswamy]

Tacker dev & user teams:

This shouldn't be a news to folks regularly attending tacker weekly
meetings.

For others, until now Tacker code base was using stable/kilo dependencies.
Now we will be switching over to use master based dependencies using [1]
and [2]. We are now close to merging these two patchsets. However this will
cause your existing devstack setups incompatible with the latest tacker
code base. Note, before merging these patchsets a stable/kilo branch will
be pulled.

Now you've two options to continue tacker activites,

1) Switch over to use new devstack setup post merge (preferred)
2) If you are in middle of something and want to continue your activity
(say a PoC in flight) consider switching tacker & python-tackerclient repo
to stable/kilo

We understand this will cause some disruption. But this is essential to cut
over to master and get ready for the upcoming liberty release.

Thanks for your support. Questions / comments welcome!

- Sridhar

[1] https://review.openstack.org/#/c/211403/
[2] https://review.openstack.org/#/c/211405/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][NFV] Tacker Liberty Midcycle meetup - Meeting Minutes

[Sridhar Ramaswamy]

Tacker team held a Liberty Midcycle meetup last week in San Jose. Thanks
everyone who took the time to participate!

The meeting minutes are captured here,

https://wiki.openstack.org/wiki/Meetings/Tacker/Liberty-Midcycle-Meeting-Minutes

The slides used in the event are available here,

http://www.slideshare.net/SridharRamaswamy/openstack-tacker-liberty-midcycle
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][NFV] No weekly IRC meeting this week

[Sridhar Ramaswamy]

Heads up.

Tacker team is holding a Liberty mid-cycle meetup this week [1]. Hence we
are cancelling our weekly IRC meeting this week on Aug 20th. The meeting
will resume next week (on Aug 27th).

[1] https://etherpad.openstack.org/p/liberty-tacker-midcycle
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][NFV] Tacker mid-cycle meetup in Aug @ San Jose

[Sridhar Ramaswamy]

Tacker team is planning a Liberty Mid-cycle meet-up.

https://etherpad.openstack.org/p/liberty-tacker-midcycle

When: Aug 20th - 21st
Where: San Jose, CA

Agenda:

Thursday Aug 20th - 1:30pm - 6pm
  - Tacker Hackathon
*for developers planning to contribute to Tacker, new members welcome!*

Friday Aug 21th - 8:30am - 5:30pm
   - Welcome / Intro / Agenda bashing
   - VNF Health Monitoring - 9am - 10:30am
   - Break
   - TOSCA / VNFD / NSD data-model - 10:45am - 12:15
   - Lunch
   - Tacker governance - spec, approval process, etc - 1:30pm - 2:30pm
   - Tacker's Service Chaining strategy - 2:30pm - 4pm
   - Wrap up

Please add your name in the etherpad if you are planning to attend.

FYI, Tacker is building an ETSI MANO based NFV Orchestrator + VNF Manager.
To learn more stop by,
 - Wiki: https://wiki.openstack.org/wiki/Tacker
 - IRC: #tacker and every Thursday @ 1600 UTC on #openstack-meeting
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][NFV] Devstack plugin support is now available

[Sridhar Ramaswamy]

Heads up. Tacker project now supports installation using a devstack plugin.
The latest Tacker installation instruction is available in this wiki [1]

Note, the team continues to meet weekly in IRC [2]. Feel free to join if
you are interested in an ETSI MANO complaint NFV Orchestrator / VNF Manager.

- Sridhar

[1] https://wiki.openstack.org/wiki/Tacker/Installation
[2] https://wiki.openstack.org/wiki/Meetings/Tacker
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker][Telco][NFV]: Reminder - weekly IRC meeting tomorrow Jun 18th

[Sridhar Ramaswamy]

Meeting on #openstack-meeting @ 1600UTC (9am PDT)

Agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_June_18.2C_2015

Feel free to update the agenda if needed.

thanks,
Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron][vpnaas] No VPNaaS weekly IRC meeting next week (June 23rd)

[Sridhar Ramaswamy]

As some of us are attending Neutron mid-cycle we are skipping the VPNaaS
weekly IRC meeting for next week Tuesday June 23rd. The meeting will resume
the week after.

As usual please update agenda on the wiki page:
https://wiki.openstack.org/wiki/Meetings/VPNaaS before the meeting.

See you all on Tuesday June 30th!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [NFV][Tacker] OpenStack based VNF Manager

[Sridhar Ramaswamy]

In some of the sessions there were questions related to VNF Manager efforts
within OpenStack. There is actually an effort to build an ETSI MANO based
VNF Manager using the stackforge project called Tacker (yes, it used to be
for ServiceVMs). Please look at the wiki below for more details,

https://wiki.openstack.org/wiki/Tacker

Also to hear more, and see a demo, there is a speaking session scheduled
for Thursday 11:50am,

http://sched.co/2qik

- Sridhar
(for Tacker team)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron][vpnaas] VPNaaS IRC meeting next Tuesday May 12th

[Sridhar Ramaswamy]

Heads up. We are planning to host an IRC meeting coming Tuesday May 12th 1600
UTC. The main agenda item is to discuss Dynamic Multipoint VPN (DMVPN)
proposal for Liberty.

For more details refer to the vpn wiki,

https://wiki.openstack.org/wiki/Meetings/VPNaaS

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev