On 11/14/2013 07:54 PM, Caitlin Bestler wrote:
> On 11/14/2013 5:12 AM, Thierry Carrez wrote:
>> Hi everyone,
>>
>> I think that we have recently reached critical mass for the
>> openstack-dev mailing-list, with 2267 messages posted in October, and
>> November well on its way to pass 2000 again.
On 11/14/2013 02:46 PM, Clint Byrum wrote:
> Excerpts from Thierry Carrez's message of 2013-11-14 05:12:55 -0800:
>> Hi everyone,
>>
>> I think that we have recently reached critical mass for the
>> openstack-dev mailing-list, with 2267 messages posted in October, and
>> November well on its way
On 11/15/2013 04:13 AM, Sylvain Bauza wrote:
> Le 14/11/2013 20:46, Clint Byrum a écrit :
>>
>> Now, choose which city will grow faster and produce more innovation.
>>
>
> The problem is larger than only innovation, it is also making sure the
> Stackforge projects are also a starting point for c
On 11/12/2013 10:15 AM, Kyle Mestery (kmestery) wrote:
> On Nov 12, 2013, at 2:46 AM, Robert Collins wrote:
>> On 12 November 2013 21:15, Edgar Magana wrote:
>>> Team,
>>>
>>> It has been decided during the Icehouse summit that all vendor specific
>>> plug-ins should enforce remote tempest tests:
On Fri, Nov 15, 2013 at 3:01 PM, Adam Young wrote:
> On 11/15/2013 11:15 AM, Ben Nemec wrote:
>
> This list is for development discussion only. Since this sounds like a
> question specific to RHEL, might I suggest you ask it on
> http://openstack.redhat.com/forum/ ?
>
>
> Nah, this is legit.
>
Hi,
On Fri, Nov 15, 2013 at 2:58 PM, Adam Young wrote:
> On 11/14/2013 07:37 PM, Avi L wrote:
>
> I have installed openstack-keystone-2013.2-0.11.b3.el6.noarch rpm and I
> added a active directory user "test123" with role admin and tenant admin
> successfully.
>
> However when I run keystone u
I would like to add that the work in forked devstack is ongoing and not
complete. I am trying to understand what would it take to push these changes
upstream such as coding requirements, testing, code organization, documentation
etc.
Thanks
Deepinder
From: Deepinder Setia mailto:dse...@junipe
great, thanks
On Sat, Nov 16, 2013 at 5:10 AM, Mark Washenberger <
mark.washenber...@markwash.net> wrote:
> Hi folks,
>
> My summary notes from the OpenStack Design Summit Glance sessions follow.
> Enjoy, and please help correct any misunderstandings.
>
>
>
> Image State Consistency:
> -
I forked devstack a few weeks ago to integrate with OpenContrail at
https://github.com/dsetia/devstack. This installs and launches OpenContrail in
addition to openstack components. OpenContrail provides network virtualization
components - SDN controller, Virtual Router and analytics - via ne
Agree with Clint completely! In my opinion it would be a big mistake to
separate the lists. There are tools in modern e-mail readers to filter
specific content into separate views. Why should OpenStack Foundation do it
for us?
Alex Freedland
Co-Founder and Chairman
Mirantis, Inc.
On Thu, Nov 1
On 2013-11-15 14:12:27 -0800 (-0800), Bhuvan Arumugam wrote:
[...]
> Can someone push 0.8.2 to pypi.openstack.org and keep unittests
> happy?
Clark just retriggered the mirror jobs manually and
pypi.openstack.org now has 0.8.2 as of ~5 minutes ago.
The mirror is usually only automatically updated
On Nov 14, 2013, at 2:02 AM, Edgar Magana wrote:
>
> I do agree with you. When I said in my first email "little bit of guidance" I
> mean the policy for Icehouse and moving forward. I do not want to make our
> PTL angry :-)
I wouldn’t worry about making me angry. I officiated football (socc
On 11/15/2013 02:38 PM, Sean Dague wrote:
Masayuki Igawa
His review history is here -
https://review.openstack.org/#/q/reviewer:masayuki.igawa%2540gmail.com+project:openstack/tempest,n,z
Ken'ichi Ohmichi
His review history is here -
https://review.openstack.org/#/q/reviewer:ken1ohmichi%2540gma
Hi,
With slight modifications of (2) one can benefit of availability:
1. There should not be a master node. Each heat engine should be able to
act as a master if someone asks it to deploy a template. Current master
engine will be responsible to contact other engines and pass them the same
template
On Fri, 15 Nov 2013 08:38:27 -0500
Sean Dague wrote:
> It's post summit time, so time to evaluate our current core group for
> Tempest. There are a few community members that I'd like to nominate
> for Tempest core, as I've found their review feedback over the last
> few months to be invaluable. T
On Fri, 2013-11-15 at 17:19 -0500, Andrew Laski wrote:
> On 11/15/13 at 07:30am, Dan Smith wrote:
> >> You're not missing anything. But I think that's a bug, or at least an
> >> unexpected change in behaviour from how it used to work. If you follow
> >> instance_update() in nova.db.sqlalchemy.api
On 11/15/2013 11:15 AM, Ben Nemec wrote:
This list is for development discussion only. Since this sounds like
a question specific to RHEL, might I suggest you ask it on
http://openstack.redhat.com/forum/ ?
Nah, this is legit.
Thanks.
-Ben
On 2013-11-15 10:13, Abhishek Lahiri wrote:
On 15/11/13 22:17, Keith Bray wrote:
The way I view 2 vs. 4 is that 2 is more complicated and you don't gain
any benefit of availability. If, in 2, your global heat endpoint is down,
you can't update the whole stack. You have to work around it by talking
to Heat (or the individual service endpo
On 11/14/2013 07:37 PM, Avi L wrote:
I have installed openstack-keystone-2013.2-0.11.b3.el6.noarch rpm and
I added a active directory user "test123" with role admin and tenant
admin successfully.
However when I run keystone user-list if gives me the following error:
Authorization Failed: An un
Hi Alejandro,
As we've already discussed the topic over IRC, let me add something else on
your setup:
- no dhcp agent, no l3 agent
- IP configuration injected into instances
(I'm disclosing this information since it's already been disclosed on IRC
whose logs are publicly accessible anyway)
Commen
On 11/14/2013 11:39 AM, Tim Hinrichs wrote:
I completely agree that making Congress successful will rely crucially on
addressing performance and scalability issues. Some thoughts...
1. We're definitely intending to cache data locally to avoid repeated API
calls. In fact, a prototype cache is
I have no particular part thus any part that need help is ok for me.
My own purpose is to support dynamic resource claim to support live migration
to instance with hardware allocated. For instance with device assigned (PCI
device, USB or everything), we can't migrate it unless it's unplugged.
A
On 11/15/13 at 07:30am, Dan Smith wrote:
You're not missing anything. But I think that's a bug, or at least an
unexpected change in behaviour from how it used to work. If you follow
instance_update() in nova.db.sqlalchemy.api just the presence of
expected_task_state triggers the check. So we m
Team,
Right now pypi.openstack.org has v0.8.1. This version of sqlalchemy-migrate
use incorrect version format 0.7.3.dev. It break unittests for several
components, nova for example.
http://pypi.openstack.org/openstack/sqlalchemy-migrate/
Apparently, David Ripton fixed it and also Monty improved i
We are all set for the Solum design workshops at SFO on Nov 19,20. The etherpad
page below has schedule and agenda details
https://etherpad.openstack.org/p/SolumSFOCommunityWorkshop
Please sign up as topic leads/scribe for the sessions listed in the agenda.
We also have etherpad pages setup for
On 11/15/2013 04:53 PM, Rochelle.Grober wrote:
Perhaps all this sound and fury will get a some entity to step up and provide
Neutron project t-shirts for the sprint;-) Then maybe the participants will
*want* to wear the Neutron Team shirt.
And as for errors, Anita, I fully understand, sympath
> -Original Message-
> From: Dan Smith [mailto:d...@danplanet.com]
> Sent: Friday, November 15, 2013 7:30 AM
> To: OpenStack Development Mailing List (not for usage questions);
> isaku.yamah...@gmail.com
> Subject: Re: [openstack-dev] [nova][api] Is this a potential issue
>
> > You're no
Perhaps all this sound and fury will get a some entity to step up and provide
Neutron project t-shirts for the sprint;-) Then maybe the participants will
*want* to wear the Neutron Team shirt.
And as for errors, Anita, I fully understand, sympathize and have experience in
that area.
--Rocky
Coming from QA/Ops, I agree that there are horizontal teams that need to get
info from the mailing list(s) across the spectrum. I also agree with Clint's
and Adrian's statements about the synergies and serendipities of all the
developers on one list. But I also understand the feeling of drowni
The way I view 2 vs. 4 is that 2 is more complicated and you don't gain
any benefit of availability. If, in 2, your global heat endpoint is down,
you can't update the whole stack. You have to work around it by talking
to Heat (or the individual service endpoints) in the region that is still
alive
Ah. Here's why.
diff --git a/neutron/tests/unit/openvswitch/test_ovs_qos.py
b/neutron/tests/unit/openvswitch/test_ovs_qos.py
index 3450b2c..8feaef4 100644
--- a/neutron/tests/unit/openvswitch/test_ovs_qos.py
+++ b/neutron/tests/unit/openvswitch/test_ovs_qos.py
@@ -32,6 +32,7 @@ class OpenvswitchQ
On Fri, Nov 15, 2013 at 11:03 AM, Dan Prince wrote:
>
>
> - Original Message -
> > From: "David Ripton"
> > To: openstack-dev@lists.openstack.org
> > Sent: Friday, November 15, 2013 1:47:58 PM
> > Subject: Re: [openstack-dev] sqlalchemy-migrate needs a new release
> >
> > On 11/15/2013 1
Hi folks,
My summary notes from the OpenStack Design Summit Glance sessions follow.
Enjoy, and please help correct any misunderstandings.
Image State Consistency:
https://etherpad.openstack.org/p/icehouse-summit-image-state-consistency
In this session, we focused on t
On 15/11/13 18:24, Bartosz Górski wrote:
Hi Thomas,
Each of the two engines will be able to create resources in both regions.
We do not need to add anything in the heat client.
Right now when you want to create a new stack (using heat client or
directly API) you need to provide:
- stack name
-
Stefan-
Your workflow is very similar to many other plugins. You’ll want to look at
implementing the port binding extension in your plugin. The port binding
extension allows Nova to inform Neutron of the host where the VM is running.
mark
On Nov 15, 2013, at 9:55 AM, Stefan Apostoaie wrot
On 11/15/2013 01:41 PM, Zane Bitter wrote:
Good news, everyone! I have created the missing whiteboard diagram
that we all needed at the design summit:
https://wiki.openstack.org/wiki/Heat/Blueprints/Multi_Region_Support_for_Heat/The_Missing_Diagram
I've documented 5 possibilities. (1) is th
Good news, everyone! I have created the missing whiteboard diagram that
we all needed at the design summit:
https://wiki.openstack.org/wiki/Heat/Blueprints/Multi_Region_Support_for_Heat/The_Missing_Diagram
I've documented 5 possibilities. (1) is the current implementation,
which we agree we wa
I also completely agree with this policy - and I hope all the developers
contributing code to non-core plugins like me will agree as well.
There is nothing like verifiability. This will also make a lot easier code
reviews for non-core plugins; one of the reasons for which these reviews
tend to have
On Fri, Nov 15, 2013 at 10:44 AM, Stephen Gran wrote:
>
>
> Surely those are local deployment policy decisions that shouldn't affect
> the development of capabilities in heat itself, right? If a deployer does
> not want one heat deployment to be able to reach some endpoints, they'll
> set up a lo
Hi,
Going back to the original message, how do you think we should proceed
with this bug? (https://review.openstack.org/#/c/55588/). Shall a new one
be created to remove the deprecated environment variables in all clients?
Thanks
Cristian
On 11/11/13 16:56, "Kevin L. Mitchell"
wrote:
>On Mon
On 11/10/2013 07:26 PM, Paul Belanger wrote:
Greeting,
In a previous thread I talked about building an application atop of
horizon and keystone. So far things are working out pretty well. One
thing I have been trying to figure out is how to move forward with
user registration for the horizon a
Zane Bitter wrote on 11/14/2013 12:56:22 PM:
> ...
> My 2c: the way I designed the Heat API was such that extant stacks can
> be addressed uniquely by name. Humans are pretty good with names, not so
> much with 128 bit numbers. The consequences of this for the design were:
> - names must be
On 11/15/2013 02:33 PM, Salvatore Orlando wrote:
Apologies for forking the thread.
Not at all. You do want you need to do.
I think this is probably the last post with some content which might
be useful for a discussion which does not involve fashion police.
I'm all for content for useful discu
On Thu, Nov 14, 2013 at 2:28 AM, Adrian Otto wrote:
> Doug,
>
> On Nov 13, 2013, at 9:28 AM, Doug Hellmann
> wrote:
>
>
>
>
> On Sun, Nov 10, 2013 at 10:15 AM, Noorul Islam K M wrote:
>
>>
>> Hello all,
>>
>> I registered a new blueprint [1] for command line client interface for
>> Solum. We ne
fyi. gate-tempest-devstack-vm-neutron-large-ops is now a bit more
stable (compare [1] and [2]) with the Nova change [3]. Joe earlier
posted a call to arms [4] yesterday.
[1]
http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkZpbmlzaGVkOiBGQUlMVVJFXCIgQU5EIGJ1aWxkX25hbWU6XCJnYXRlLXRlbXBlc3QtZGV2c3Rh
Apologies for forking the thread.
I think this is probably the last post with some content which might be
useful for a discussion which does not involve fashion police.
On another note, I've seen my name is in the list of the required
attendees. To be fair and honest I'm not any more required than
On Fri, Nov 15, 2013 at 9:01 AM, Mark McLoughlin wrote:
> On Fri, 2013-11-15 at 11:28 -0500, Russell Bryant wrote:
> > Greetings,
> >
> > We've talked a lot about requirements for new compute drivers [1]. I
> > think the same sort of standards shold be applied for a new third-party
> > API, such
On 11/15/2013 01:26 PM, Lorin Hochstein wrote:
> Was the fate of nova-network discussed at the icehouse summit?
Yes. [1][2]
> In particular, has there been a decision made about whether it will
> definitely be deprecated in some (as yet unspecified) future release, or
> whether it will continue t
On 15/11/13 18:55, terryxing wrote:
Hi Dear All,
I am wondering that is there any way in Openstack to know when new
instance is created ? is there any Python API to do this ? Since I want
to monitor the instance creation event and trigger another event, thus,
my program needs to be know wheneve
- Original Message -
> Hi Dear All,
>
> I am wondering that is there any way in Openstack to know when new instance
> is created ? is there any Python API to do this ? Since I want to monitor
> the instance creation event and trigger another event, thus, my program
> needs to be know whe
On 11/15/2013 12:24 PM, Bartosz Górski wrote:
> Hi Thomas,
>
> Each of the two engines will be able to create resources in both regions.
> We do not need to add anything in the heat client.
>
> Right now when you want to create a new stack (using heat client or
> directly API) you need to provi
Russell Bryant wrote on 15/11/2013 06:49:31 PM:
> 3) If you have work planned for Icehouse, please get your blueprints
> filed as soon as possible. Be sure to set a realistic target milestone.
> So far, *everyone* has targeted *everything* to icehouse-1, which is
> set to be released in less th
- Original Message -
> From: "David Ripton"
> To: openstack-dev@lists.openstack.org
> Sent: Friday, November 15, 2013 1:47:58 PM
> Subject: Re: [openstack-dev] sqlalchemy-migrate needs a new release
>
> On 11/15/2013 10:41 AM, David Ripton wrote:
>
> > sqlalchemy-migrate-0.8.1 is now u
Hi Dear All,
I am wondering that is there any way in Openstack to know when new
instance is created ? is there any Python API to do this ? Since I want to
monitor the instance creation event and trigger another event, thus, my
program needs to be know whenever a new instance is created.
I can ru
On 11/15/2013 11:15 AM, Jason Dunsmore wrote:
Great description of Heat vs. Solum! This belongs in the FAQs of both
projects IMO. This question is bound to keep coming up (for good
reason).
Indeed, Angus' descriptions as well as many of the other folks on this
thread were great and definitel
On 11/15/2013 10:41 AM, David Ripton wrote:
sqlalchemy-migrate-0.8.1 is now up on PyPI. Thanks fungi for kicking
PyPI for me.
So there was a hardcoded version number inside migrate/__init__.py,
which broke things when I didn't manually update it to sync with the new
release's version number
On 15/11/13 18:35, Georgy Okrokvertskhov wrote:
First of all, I believe this approach assumes that heat engine can reach
API endpoints which are located in different region. I am not sure if it
is a default deployment approach when someone is exposing OpenStack
services endpoints to the outside o
Hi Bartosz,
Could you please clarify the section about resource creation in other
regions via calling their endpoints?
>So from heat engine point of view there is not big change in the workflow.
Heat will parse the template, >create the
>dependencies graph and start creating resources in the same
On 11/15/2013 01:13 PM, Mark McLoughlin wrote:
On Fri, 2013-11-15 at 12:47 -0500, Anita Kuno wrote:
On 11/15/2013 12:34 PM, Russell Bryant wrote:
On 11/15/2013 12:16 PM, Kyle Mestery (kmestery) wrote:
On Nov 15, 2013, at 11:04 AM, Dan Smith wrote:
Thanks for weighing in, I do hope to keep th
On 11/15/2013 12:58 PM, Russell Bryant wrote:
On 11/15/2013 12:47 PM, Anita Kuno wrote:
I will also note, that while you clearly stated the Neutron is being
considered for deprecation - t-shirts prevail as an issue on this
thread. I consider that rather interesting to observe.
Believe me, I'd m
Was the fate of nova-network discussed at the icehouse summit?
In particular, has there been a decision made about whether it will
definitely be deprecated in some (as yet unspecified) future release, or
whether it will continue to be supported for the foreseeable future?
Lorin
--
Lorin Hochstei
Another thing that I remember from talking with people who work at yahoo
on the hadoop project and was an insight early on for me. I remember those
folks saying that about 2 hours of there day is spent on catching up on
mailing list emails and reviews. This is/was a change in how they operated
when
On Fri, 2013-11-15 at 12:47 -0500, Anita Kuno wrote:
> On 11/15/2013 12:34 PM, Russell Bryant wrote:
> > On 11/15/2013 12:16 PM, Kyle Mestery (kmestery) wrote:
> >> On Nov 15, 2013, at 11:04 AM, Dan Smith wrote:
> Thanks for weighing in, I do hope to keep the conversation going.
> >>> Add my
On Nov 15, 2013 9:36 AM, "Matt Riedemann"
wrote:
>
>
>
> On 11/15/2013 10:15 AM, Matt Riedemann wrote:
>>
>>
>>
>> On 11/14/2013 10:38 PM, Matt Riedemann wrote:
>>>
>>> Joe,
>>>
>>> Hey, I missed this question. I moved email accounts for the
>>> openstack-dev mailing list and missed this in my ol
Hi Vish,
Thank you very much indeed for your reply!
>From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
>Sent: 12 November 2013 21:56
>To: OpenStack Development Mailing List (not for usage questions)
>Subject: Re: [openstack-dev] Nova XML serialization bug 1223358 moving
>discussion here to
On Wed, 2013-11-13 at 06:57 -0500, Sean Dague wrote:
> (Apologies, this started on the TC list, and really should have started
> on -dev, correctly posting here now for open discussion)
>
> There were a few chats at summit about this, mostly on the infra /
> devstack / qa side of the house. Consid
On 11/15/2013 12:47 PM, Anita Kuno wrote:
> I will also note, that while you clearly stated the Neutron is being
> considered for deprecation - t-shirts prevail as an issue on this
> thread. I consider that rather interesting to observe.
Believe me, I'd much rather be able to focus on what actuall
On 11/15/2013 12:32 PM, Mark McLoughlin wrote:
>> If so, do we apply the same standards to the EC2 API?
>> How much time do we give EC2 to get up to this standard before we rip
>> it out?
>
> I hadn't understood the EC2 API to be in such a woeful state. Are we
> saying the implementation is so bad
Excerpts from Stefano Maffulli's message of 2013-11-15 09:12:05 -0800:
> On 11/15/2013 02:06 AM, Thierry Carrez wrote:
> > Arguments in favor of splitting openstack-dev / stackforge-dev
> > * People can easily filter out all non-openstack discussions
> > * Traffic would drop by about 25%
>
> I'm n
On 11/15/2013 12:34 PM, Russell Bryant wrote:
On 11/15/2013 12:16 PM, Kyle Mestery (kmestery) wrote:
On Nov 15, 2013, at 11:04 AM, Dan Smith wrote:
Thanks for weighing in, I do hope to keep the conversation going.
Add my name to the list of people that won't be considering the trip as
a resul
I fired up the tests in a virtual machine, and when you run the full
tox - it'll error out like Jenkins does, but when you run
just the one module of tests by itself, it passes.
http://paste.openstack.org/show/53159/
--
Sean M. Collins
___
OpenStack-de
On Nov 15, 2013, at 11:34 AM, Russell Bryant wrote:
> On 11/15/2013 12:16 PM, Kyle Mestery (kmestery) wrote:
>> On Nov 15, 2013, at 11:04 AM, Dan Smith wrote:
Thanks for weighing in, I do hope to keep the conversation going.
>>>
>>> Add my name to the list of people that won't be considerin
Erik,
correct, savanna-image-elements is the right place for your dib elements. There
is no need to separate vanilla and hdp elements to different sub packages but
btw it could be easily done by appending ELEMENTS_PATH as Clint said.
Sincerely yours,
Sergey Lukjanov
Savanna Technical Lead
Miran
On 11/15/2013 12:16 PM, Kyle Mestery (kmestery) wrote:
> On Nov 15, 2013, at 11:04 AM, Dan Smith wrote:
>>> Thanks for weighing in, I do hope to keep the conversation going.
>>
>> Add my name to the list of people that won't be considering the trip as
>> a result.
>>
> Are people really saying tha
On 11/15/2013 10:15 AM, Matt Riedemann wrote:
On 11/14/2013 10:38 PM, Matt Riedemann wrote:
Joe,
Hey, I missed this question. I moved email accounts for the
openstack-dev mailing list and missed this in my old pile.
So I touched on this a bit in response here [1] and also a bit when
talki
On Fri, 2013-11-15 at 12:19 -0500, Russell Bryant wrote:
> On 11/15/2013 12:01 PM, Mark McLoughlin wrote:
> > On Fri, 2013-11-15 at 11:28 -0500, Russell Bryant wrote:
> >> Greetings,
> >>
> >> We've talked a lot about requirements for new compute drivers [1]. I
> >> think the same sort of standard
Hi Thomas,
Each of the two engines will be able to create resources in both regions.
We do not need to add anything in the heat client.
Right now when you want to create a new stack (using heat client or
directly API) you need to provide:
- stack name
- template
- parameters (if need)
- tenant
On 11/15/2013 12:14 PM, Clint Byrum wrote:
Excerpts from Erik Bergenholtz's message of 2013-11-15 08:20:36 -0800:
Team -
We’d like to move our disk creation mechanism over to using DiskBuilder so that
users can build (and modify) their own VM images. We’d like to piggy back off
of the existin
On 11/15/2013 12:01 PM, Mark McLoughlin wrote:
> On Fri, 2013-11-15 at 11:28 -0500, Russell Bryant wrote:
>> Greetings,
>>
>> We've talked a lot about requirements for new compute drivers [1]. I
>> think the same sort of standards shold be applied for a new third-party
>> API, such as the GCE API
It sounds like you're looking for barbican :)
https://github.com/stackforge/barbican
On Thu, Nov 14, 2013 at 8:55 PM, Nachi Ueno wrote:
> Hi Keystone guys
>
> I'm going to use keystone credentials API to store SSL-VPN certificate.
> However I have a concern about blob attribute.
>
> Since i
On 11/15/2013 12:04 PM, Dan Smith wrote:
Thanks for weighing in, I do hope to keep the conversation going.
Add my name to the list of people that won't be considering the trip as
a result.
--Dan
I acknowledge your choice, Dan.
Thanks,
Anita.
___
On Nov 15, 2013, at 11:04 AM, Dan Smith wrote:
>> Thanks for weighing in, I do hope to keep the conversation going.
>
> Add my name to the list of people that won't be considering the trip as
> a result.
>
Are people really saying that if they show up for this Tempest sprint
with a logo shirt th
Excerpts from Erik Bergenholtz's message of 2013-11-15 08:20:36 -0800:
> Team -
>
> We’d like to move our disk creation mechanism over to using DiskBuilder so
> that users can build (and modify) their own VM images. We’d like to piggy
> back off of the existing mechanism that the vanilla plugin
Ilya, Igor
I’ve created separate etherpad for UnifiedAgents approach:
https://etherpad.openstack.org/p/UnifiedAgents
I described here initial Savanna's requirements from GuestAgent solution which
were discussed in the design summit.
Trove and Murano team are welcome to describe their needs in gu
On Wed, Nov 13, 2013 at 4:28 PM, Doug Hellmann
wrote:
> The Oslo team will meet in #openstack-meeting this Friday at 1400 UTC to
> discuss the i18n work and planning based on the outcome of the summit. See
> https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting for
> a more detaile
During our meeting today, we talked about how to track the graduation
status for the incubator code. I copied the notes from the summit session
where we talked about the status of a lot of the modules into a wiki page
for longer-term tracking (
https://wiki.openstack.org/wiki/Oslo/GraduationStatus)
On 11/15/2013 02:06 AM, Thierry Carrez wrote:
> Arguments in favor of splitting openstack-dev / stackforge-dev
> * People can easily filter out all non-openstack discussions
> * Traffic would drop by about 25%
I'm not so convinced about this figure, as others pointed out.
> * Removes confusion as
Adrian Otto wrote:
> If OpenStack starts a culture of exclusion instead of inclusion, that would
> start a dangerous trend that sets the wrong tone. It would quickly reach the
> point where new projects like mine would simply not come here. We would go
> somewhere else that does have a culture o
> Thanks for weighing in, I do hope to keep the conversation going.
Add my name to the list of people that won't be considering the trip as
a result.
--Dan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi
On Fri, 2013-11-15 at 11:28 -0500, Russell Bryant wrote:
> Greetings,
>
> We've talked a lot about requirements for new compute drivers [1]. I
> think the same sort of standards shold be applied for a new third-party
> API, such as the GCE API [2].
>
> Before we can consider taking on a new API,
Greetings,
I've received a lot of requests for blueprint reviews in the last week
(on the list, IRC, direct email, etc). I figured now was a good time to
recap where we are with Icehouse blueprints.
1) We've had a discussion both on the mailing list [1] and at the design
summit [2] about the pro
+1 for Ken'ichi and Masayuki
Sorry to see Jay go :-(
-David
On 11/15/2013 08:38 AM, Sean Dague wrote:
It's post summit time, so time to evaluate our current core group for
Tempest. There are a few community members that I'd like to nominate for
Tempest core, as I've found their review feedback
Greetings,
We've talked a lot about requirements for new compute drivers [1]. I
think the same sort of standards shold be applied for a new third-party
API, such as the GCE API [2].
Before we can consider taking on a new API, it should have full test
suite coverage. Ideally this would be extens
This list is for development discussion only. Since this sounds like a
question specific to RHEL, might I suggest you ask it on
http://openstack.redhat.com/forum/ ?
Thanks.
-Ben
On 2013-11-15 10:13, Abhishek Lahiri wrote:
>> I have installed openstack-keystone-2013.2-0.11.b3.el6.noarch r
Hey,
Awesome! Thank you, guys!
I'm going to give it a try early next week (we basically need to
run/fix tests for every project that uses sqlalchemy-migrate before we
can bump the version in global-requirements, but at least we can start
doing this now).
Roman
On Fri, Nov 15, 2013 at 5:41 PM, D
Team -
We’d like to move our disk creation mechanism over to using DiskBuilder so that
users can build (and modify) their own VM images. We’d like to piggy back off
of the existing mechanism that the vanilla plugin uses. It looks like I should
be able to add image-elements to savanna-image-ele
On 11/15/2013 11:01 AM, Kyle Mestery (kmestery) wrote:
On Nov 15, 2013, at 9:36 AM, Russell Bryant wrote:
On 11/13/2013 11:10 AM, Anita Kuno wrote:
Neutron Tempest code sprint
In the second week of January in Montreal, Quebec, Canadathere will be a
Neutron Tempest code sprint to improve the s
On 11/14/2013 10:38 PM, Matt Riedemann wrote:
Joe,
Hey, I missed this question. I moved email accounts for the
openstack-dev mailing list and missed this in my old pile.
So I touched on this a bit in response here [1] and also a bit when
talking about the plans for CI for the nova PowerVM vi
Great description of Heat vs. Solum! This belongs in the FAQs of both
projects IMO. This question is bound to keep coming up (for good
reason).
On Thu, Nov 14 2013, Angus Salkeld wrote:
> On 14/11/13 13:41 -0500, Jay Pipes wrote:
>>So while I have been on vacation, I've been thinking about Solu
> I have installed openstack-keystone-2013.2-0.11.b3.el6.noarch rpm and I added
> a active directory user "test123" with role admin and tenant admin
> successfully. In Keystone.conf identity is pointed to ldap and assignment is
> pointed to SQL. I sourced keystonerc file with the correct cred
1 - 100 of 177 matches
Mail list logo
