Re: [openstack-dev] [puppet] New Puppet module for Tacker Project

[Dan Radez]

On 11/07/2015 02:24 PM, Emilien Macchi wrote:
> 
> 
> On 11/07/2015 05:29 AM, Dan Radez wrote:
>> I've recently become involved in the Tacker project:
>> https://wiki.openstack.org/wiki/Tacker
>>
>> I have been deploying with puppet and collected some puppet code that I
>> would like to push openstack in a new puppet module puppet-tacker.
>>
>> I've begun to collect the code here:
>> https://github.com/radez/puppet-tacker
>>
>> I've just found the page on the openstack puppet wiki about using cookie
>> cutter and modulesync. I start that process now, was interested to get a
>> mailing list discussion going. I'll be sure to complete it before I push
>> any code into openstack repos.
>>
> 
> Hey Dan,
> 
> Thanks for putting this effort in our community!
> Every new module has to follow this process:
> https://wiki.openstack.org/wiki/Puppet/New_module
> 
> So we make sure our modules are consistent and compliant with our way to
> develop Puppet modules.
> 
> In your case, I suggest to
> 1/ move the module to OpenStack namespace
> 2/ submit the patch in Governance to add the new repo, though I'm not
> sure this module can be "big tent", since afik Tacker is not big tent.
> We'll figure out with TC.
> 3/ Adapt your module with our Wiki page documentation, and the tool we use.
> 
> I'm off next week, but don't hesitate to come up on #puppet-openstack
> (freenode) and ask for help.
> 
> Emilien
> 
> __
> 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
> 


Ah, I got this backwards, I understood that it would be moved to
openstack namespace after it's "accepted"

Thanks for the direction, I'll make some progress on this and be back in
touch.

Dan

__
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] [nova] Proposal to add Alex Xu to nova-core

[Gary Kotton]

+1. Well deserved!




On 11/8/15, 7:28 AM, "GHANSHYAM MANN"  wrote:

>I am not core but Big +1 for Alex. It will be great to have him in nova core.
>
>Thanks
>ghanshyam
>
>On Sat, Nov 7, 2015 at 12:32 AM, John Garbutt  wrote:
>> Hi,
>>
>> I propose we add Alex Xu[1] to nova-core.
>>
>> Over the last few cycles he has consistently been doing great work,
>> including some quality reviews, particularly around the API.
>>
>> Please respond with comments, +1s, or objections within one week.
>>
>> Many thanks,
>> John
>>
>> [1]https://urldefense.proofpoint.com/v2/url?u=http-3A__stackalytics.com_-3Fmodule-3Dnova-2Dgroup-26user-5Fid-3Dxuhj-26release-3Dall&d=BQICAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=I6K1mUZdPh00K3d5u0cyggblQoCmHIkG4N2Mqq-Ljyg&s=2SjmdVLDR0ANw53lGaR9I4gwUYUiq81gTvfcfMkWefw&e=
>>  
>>
>> __
>> 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
>
>
>
>-- 
>Regards
>Ghanshyam Mann
>+81-8084200646
>
>__
>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 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

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  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

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

[GHANSHYAM MANN]

I am not core but Big +1 for Alex. It will be great to have him in nova core.

Thanks
ghanshyam

On Sat, Nov 7, 2015 at 12:32 AM, John Garbutt  wrote:
> Hi,
>
> I propose we add Alex Xu[1] to nova-core.
>
> Over the last few cycles he has consistently been doing great work,
> including some quality reviews, particularly around the API.
>
> Please respond with comments, +1s, or objections within one week.
>
> Many thanks,
> John
>
> [1]http://stackalytics.com/?module=nova-group&user_id=xuhj&release=all
>
> __
> 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



-- 
Regards
Ghanshyam Mann
+81-8084200646

__
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] - Monitoring VLAN/Compute bandwidth

[sgzoh...@campus.technion.ac.il]

Hi all,


I'd like your opinion please regarding developing a Neutron plugin for 
monitoring (or estimating) bandwidth going through VLANs and Computes, without 
having to monitor any specific VM bandwidth.


I've started doing this myself using sFlow, which of course only estimates 
these figures.


Using sFlow, It should be quite simple to add this to Neutron as plugin.


Would this be useful as a Neutron service plugin?


--

Gilad Zohari
__
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] [puppet] weekly meeting #58 and next week

[Emilien Macchi]

Hello!

Here's an initial agenda for our weekly meeting, Tuesday at 1500 UTC
in #openstack-meeting-4:

https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151110

I'm off all next week (holidays without IRC, and rare access to
e-mails...), so mfish will be chair.

During the week, if you have any problem with Puppet CI, you can ping
degorenko on IRC.
When I come back, I'll work on 7.0.0 release to create our
stable/liberty branch.

Thanks and see you soon,
Emilien

__
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] New Puppet module for Tacker Project

[Emilien Macchi]

On 11/07/2015 05:29 AM, Dan Radez wrote:
> I've recently become involved in the Tacker project:
> https://wiki.openstack.org/wiki/Tacker
> 
> I have been deploying with puppet and collected some puppet code that I
> would like to push openstack in a new puppet module puppet-tacker.
> 
> I've begun to collect the code here:
> https://github.com/radez/puppet-tacker
> 
> I've just found the page on the openstack puppet wiki about using cookie
> cutter and modulesync. I start that process now, was interested to get a
> mailing list discussion going. I'll be sure to complete it before I push
> any code into openstack repos.
> 

Hey Dan,

Thanks for putting this effort in our community!
Every new module has to follow this process:
https://wiki.openstack.org/wiki/Puppet/New_module

So we make sure our modules are consistent and compliant with our way to
develop Puppet modules.

In your case, I suggest to
1/ move the module to OpenStack namespace
2/ submit the patch in Governance to add the new repo, though I'm not
sure this module can be "big tent", since afik Tacker is not big tent.
We'll figure out with TC.
3/ Adapt your module with our Wiki page documentation, and the tool we use.

I'm off next week, but don't hesitate to come up on #puppet-openstack
(freenode) and ask for help.

Emilien

__
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] [Zaqar] OpenStack Tokyo Summit Summary

[Fei Long Wang]

Thanks, Doug. I will talk with Ceilometer team to see what we can do.

On 07/11/15 07:36, Doug Hellmann wrote:

Excerpts from Fei Long Wang's message of 2015-11-07 01:31:09 +1300:

Greetings,

Firstly, thank you for everyone joined Zaqar sessions at Tokyo summit.
We definitely made some great progress for those working sessions. Here
are the high level summary and those are basically our Mitaka
priorities. I may miss something so please feel free to comment/reply
this mail.

Sahara + Zaqar
-

We have a great discussion with Ethan Gafford from Sahara team. Sahara
team is happy to use Zaqar to fix some potential security issues. The
main user case will be covered in Mitaka is protecting tenant guest and
data from administrative user. So what Zaqar team needs to do in Mitaka
is completing the zaqar client function gaps for v2 to support signed
URL, which will be used by Sahara guest agent. Ethan will create a spec
in Sahara to track this work. This is a POC of what it'd look like to
have a guest agent in Sahara on top of Zaqar. The Sahara team has not
decided to use Zaqar yet but this would be the bases for that discussion.

Horizon + Zaqar
--

We used 1 horizon work session and 1 Zaqar work session to discuss this
topic. The main user case we would like to address is the async
notification so that Horizon won't have to poll the other OpenStack
components(e.g. Nova, Glance or Cinder) per second to get the latest
status. And I'm really happy to see we worked out a basic plan by
leveraging Zaqar's notification and websocket.

1. Implement a basic filter for Zaqar subscription, so that Zaqar can
decide if the message should be posted/forwarded to the subscriber when
there is a new message posted the queue. With this feature, Horizon will
only be notified by its interested notifications.

https://blueprints.launchpad.net/zaqar/+spec/suport-filter-for-subscription

2. Listen OpenStack notifications

We may need more discussion about this to make sure if it should be in
the scope of Zaqar's services. It could be separated process/service of
Zaqar to listen/collect interested notifications/messages and post them
in to particular Zaqar queues. It sounds very interesting and useful but
we need to define the scope carefully for sure.

The Telemetry team discussed splitting out the code in Ceilometer that
listens for notifications to make it a more generic service that accepts
plugins to process events. One such plugin might be an interface to
filter events and republish them to Zaqar, so if you're interested in
working on that you might want to coordinate with the Telemetry team to
avoid duplicating effort.



Pool Group and Flavor
-

Thanks MD MADEEM proposed this topic so that we have a chance to review
the design of pool, pool group and flavor. Now the pool group and flavor
has a 1:1 mapping relationship and the pool group and pool has a 1:n
mapping relationship. But end user don't know the existence of pool, so
flavor is the way for end user to select what kind of storage(based on
capabilities) he want to use. Since pool group can't provide more
information than flavor so it's not really necessary, so we decide to
deprecate/remove it in Mitaka. Given this is hidden from users (done
automatically by Zaqar), there won't be an impact on the end user and
the API backwards compatibility will be kept.

https://blueprints.launchpad.net/zaqar/+spec/deprecate-pool-group

Zaqar Client


Some function gaps need to be filled in Mitaka. Personally, I would rate
the client work as the 1st priority of M since it's very key for the
integration with other OpenStack components. For v1.1, the support for
pool and flavor hasn't been completed. For v2, we're stilling missing
the support for subscription and signed URL.

https://blueprints.launchpad.net/zaqar/+spec/finish-client-support-for-v1.1-features

SqlAlchemy Migration
-

Now we're missing the db migration support for SqlAlchemy, the control
plane driver. We will fix it in M as well.

https://blueprints.launchpad.net/zaqar/+spec/sqlalchemy-migration



Guys, please contribute this thread to fill the points/things I missed
or pop up in #openstack-zaqar channel directly with questions and
suggestions.


__
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


--
Cheers & Best regards,
Fei Long Wang (王飞龙)
--
Senior Cloud Software Engineer
Tel: +64-48032246
Email: flw...@catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
---

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

[Andreas Jaeger]

On 11/03/2015 08:46 PM, Doug Hellmann wrote:

[...]
We are ready to start rolling out Reno for use with Liberty stable
branch releases and in master for the Mitaka release. We need the
release liaisons to create and merge a few patches for each project
between now and the Mitaka-1 milestone.

1. We need one patch to the master branch of the project to add the
instructions for publishing the notes as part of the project
sphinx documentation build.  An example patch for Glance is in
[2].

2. We need another patch to the stable/liberty branch of the project
to set up Reno and introduce the first release note for that
series. An example patch for Glance is in [3].

> [...]

What shall we do with projects that do not have a stable/liberty? For 
example openstack-doc-tools does not have one and we hope we don't need one?


Does the following look ok?
https://review.openstack.org/242748

Also, what do you think of adding this to openstack-manuals? We do not 
tag releases for the manuals but release continously. Will the tools 
work fine here?


Andreas
--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

[Sean M. Collins]

Learn from my mistake, check your calendar for the timezone if you've
created an event for the weekly meetings. Google makes it a hassle to
set things in UTC time, so I was caught by surprise by the FwaaS meeting
due to the DST change in the US of A.

-- 
Sean M. Collins

__
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] Planning and prioritizing session for Mitaka

[Lingxian Kong]

Hi, Renat, thanks for bringing this, the time works for me as well.

On Thu, Nov 5, 2015 at 3:23 PM, Renat Akhmerov  wrote:
> Team,
>
> We’ve done a great job at the summit discussing our most hot topics within 
> the project and a lot of important decisions were made. I would like to have 
> though one more session in IRC to wrap up this by going over all the BPs/bugs 
> we created in order to scope and prioritize them.
>
> I’m proposing next Monday 9 Nov at 7.00 UTC. If you have other time options 
> let’s communicate.
>
> Thanks
>
> Renat Akhmerov
> @ Mirantis Inc.
>
>
>
>
> __
> 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



-- 
Regards!
---
Lingxian Kong

__
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] New Puppet module for Tacker Project

[Dan Radez]

Thanks for the quick reply Iury,
I'll try to make it this upcoming Tuesday, I'll be travelling so I may
not be able to make it.

If not I'll definitely join the following week.

Thanks

Dan Radez
irc: radez

On 11/07/2015 07:17 AM, Iury Gregory wrote:
> Hi Dan,
> 
> Nice to hear about a new puppet-module =)
> You can contact puppet guys on #puppet-openstack irc channel.
> Our weekly meeting occurs every Tuesday at 15 UTC in #openstack-meeting-4.
> 
> Welcome!
> 
> 
> 2015-11-07 7:29 GMT-03:00 Dan Radez  >:
> 
> I've recently become involved in the Tacker project:
> https://wiki.openstack.org/wiki/Tacker
> 
> I have been deploying with puppet and collected some puppet code that I
> would like to push openstack in a new puppet module puppet-tacker.
> 
> I've begun to collect the code here:
> https://github.com/radez/puppet-tacker
> 
> I've just found the page on the openstack puppet wiki about using cookie
> cutter and modulesync. I start that process now, was interested to get a
> mailing list discussion going. I'll be sure to complete it before I push
> any code into openstack repos.
> 
> Thanks
> 
> Dan 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

Re: [openstack-dev] [openstack-ansible][security] Next steps: openstack-ansible-security

[McPeak, Travis]

Hey Major,

This sounds like a great next step.  It might also be cool to set up
Vagrant to pull Ubuntu 14.04, grab Ansible, and run the scripts on it.
I'll carve out a few hours early next week and have a crack at it.

-Travis




On 11/6/15, 10:59 PM, Major Hayden wrote:

>Hello there,
>
>At this moment, openstack-ansible-security[1] is feature complete and
>all of the Ansible tasks and documentation for the STIGs are merged.
>Exciting!
>
>I've done lots of work to ensure that the role uses sane defaults so
>that it can be applied to the majority of OpenStack deployments without
>disrupting services.  It only supports Ubuntu 14.04 for now, but that's
>openstack-ansible's supported platform as well.
>
>I'd like to start by adding it to the gate-check-commit.sh script so
>that the security configurations are applied prior to running tempest.
>This should hopefully catch any defaults that could be disruptive in an
>openstack-ansible environment.  If that works, I'd like to add it to
>the run-playbooks.sh script so that it runs for all deployments
>(toggled via a configuration option, of course).
>
>Does that seem like a decent plan?  Let me know if that makes sense
>and I'll get to work.

smime.p7s
Description: S/MIME cryptographic signature
__
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] [puppet] New Puppet module for Tacker Project

[Dan Radez]

I've recently become involved in the Tacker project:
https://wiki.openstack.org/wiki/Tacker

I have been deploying with puppet and collected some puppet code that I
would like to push openstack in a new puppet module puppet-tacker.

I've begun to collect the code here:
https://github.com/radez/puppet-tacker

I've just found the page on the openstack puppet wiki about using cookie
cutter and modulesync. I start that process now, was interested to get a
mailing list discussion going. I'll be sure to complete it before I push
any code into openstack repos.

Thanks

Dan 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