I've got a new tool, currently called prep-source-repos, that I'd like to
set up as a new project. Most of the work was done by adamg and lifeless,
with a bit of polish from me to make it ready to be packaged.
The tool is something the tripleo-cd-admins have been using to let us
deploy a cloud fro
confirmed
On 10/10/2014 01:52 AM, David Lyle wrote:
> I would like to announce my candidacy for the Technical Committee.
>
> I have been working on OpenStack since the beginning of the Grizzly cycle.
> I started working on OpenStack as part of HP's Public Cloud effort. I spent
> two years working
Hi team,
After several discussions i want to propose generic format
for describing deployment tasks, this format is expected to cover
all tasks (e.g pre-deployment and post-deployment), also it should cover
different actions like upgrade/patching
action: upload_file
id: upload_astute
roles: *
para
Hi Everett,
Great to see things moving with the API Working Group!
On Thu, Oct 9, 2014 at 9:35 AM, Everett Toews
wrote:
> https://wiki.openstack.org/wiki/API_Working_Group
>
> This is the start of the API Working Group (API WG).
>
> To avoid bike shedding over the name of the working group, I d
confirmed
On 10/10/2014 01:22 AM, John Griffith wrote:
> I'd like to announce my candidacy for the OpenStack Technical Committee
> Fall 2014 elections.
>
> I've been contributing to OpenStack for almost three years now (this months
> my anniversary) and up until this election cycle have served as
I would like to announce my candidacy for the Technical Committee.
I have been working on OpenStack since the beginning of the Grizzly cycle.
I started working on OpenStack as part of HP's Public Cloud effort. I spent
two years working to make Horizon work in that scale of environment and
making H
I'd like to announce my candidacy for the OpenStack Technical Committee
Fall 2014 elections.
I've been contributing to OpenStack for almost three years now (this months
my anniversary) and up until this election cycle have served as PTL for the
Cinder Project. Over the years I've had the opportun
Hi Swift folks,
Today the following patch was abandoned and I contacted with the author,
so I would like to take it over if nobody else is chafing to take it.
Is it OK?
https://review.openstack.org/#/c/80421/
If it is OK, I will proceed it with following procedure.
(1) Open new bug report (the
Hello, Duncan,
You are right. It's not simple multiplier game.
The performance or scalability bottleneck is mainly impacted from two aspect:
request concurrency to the cloud, and the volume of the objects (including
VM,Volume,Port,etc).
We can discuss that in a scenario: there are 1 million V
Hope this can accelerate Neutron's development :-)
Regards,
Damon
2014-10-09 5:46 GMT+08:00 Kyle Mestery :
> Sure, I'll add that section there.
>
> On Tue, Oct 7, 2014 at 2:58 PM, Kevin Benton wrote:
> > Can you add a section to the wiki to document how a core can become a
> member
> > of the d
Yes. That will be more safer.
On Fri, Oct 10, 2014 at 12:00 AM, Nader Lahouti wrote:
> Thanks Lei for the reply and clarification.
> So, instead of that we can use the following:
>
>
> from keystone client.v2_0 import Client
>
> keystone = Client(username=user, password=password, tenant_name=tena
> On 10 Oct 2014, at 07:32, Gregory Haynes wrote:
>
> Hello TripleO-ers,
>
> Last time around there was a lot of feedback that we should plan our
> mid-cycle metup a lot sooner, so lets do that! I've created a (mostly
> bare) etherpad here:
>
> https://etherpad.openstack.org/p/kilo-tripleo-
What about using graphite + logstash to power a post-job
/nightly-job/post-merge-periodic (the new thing we talked about in Germany)
dashboard?
There are a few different use cases for a dashboard for jobs that don't
report on gerrit changes.
* Track the success an failure rates over time
* If I
On 10/09/2014 02:39 PM, Jeremy Stanley wrote:
On 2014-10-09 11:31:37 -0600 (-0600), Chris Friesen wrote:
Just curious...why do we remove the stable branches for old
releases? Is the idea to force people onto new branches?
It's twofold. First, it's to indicate that the branch will be
getting no
Meeting minutes:
http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-10-09-18.02.html
On Wed, Oct 8, 2014 at 10:59 AM, Sergey Lukjanov
wrote:
> Hi folks,
>
> We'll be having the Sahara team meeting as usual in
> #openstack-meeting-alt channel.
>
> Agenda:
> https://wiki.openstack.org
On Oct 9, 2014, at 4:30 PM, Matt Riedemann wrote:
> The sqlalchemy-migrate project is basically maintenance mode and the core
> team [1] is kind of a weird mix of people - all great people I'm sure, but I
> think it's more a team of people that stepped up when OpenStack took over the
> projec
On 10/9/2014 3:30 PM, Matt Riedemann wrote:
The sqlalchemy-migrate project is basically maintenance mode and the
core team [1] is kind of a weird mix of people - all great people I'm
sure, but I think it's more a team of people that stepped up when
OpenStack took over the project and said they'
On 2014-10-09 14:13:29 -0400 (-0400), Boden Russell wrote:
> If I'm not mistaken; it appears the tag rename from "havana" ->
> "havana-eol" may be effecting the upgrade CI tests in recent
> commits (ex: [1]).
>
> For example in real-db-upgrade_nova_mysql_user001:th-mysql:
[...]
That's a third-par
On 2014-10-09 11:31:37 -0600 (-0600), Chris Friesen wrote:
> Just curious...why do we remove the stable branches for old
> releases? Is the idea to force people onto new branches?
It's twofold. First, it's to indicate that the branch will be
getting no new patches ever. Second, it's because that's
Hello TripleO-ers,
Last time around there was a lot of feedback that we should plan our
mid-cycle metup a lot sooner, so lets do that! I've created a (mostly
bare) etherpad here:
https://etherpad.openstack.org/p/kilo-tripleo-midcycle-meetup
Note that there are currently no possible venues listed
The sqlalchemy-migrate project is basically maintenance mode and the
core team [1] is kind of a weird mix of people - all great people I'm
sure, but I think it's more a team of people that stepped up when
OpenStack took over the project and said they'd babysit it but it's
pretty idle.
Given w
Documented in the Wiki:
https://wiki.openstack.org/wiki/Fuel/Code_Review_Rules#Merging_commits
On Thu, Oct 9, 2014 at 1:19 AM, Mike Scherbakov
wrote:
> This discussion should go in the public, as not every developer is here,
> and other opinions are important.
>
> I believe that we are again div
On Oct 8, 2014, at 10:14 AM, Doug Hellmann wrote:
>
> On Oct 8, 2014, at 1:22 AM, Robert Collins wrote:
>
>> On 8 October 2014 11:10, Mike Bayer wrote:
>>> Hi folks -
>>>
>>> So just to update on the status here, for the transactional testing and all
>>> that, I’ve had a blueprint in the q
Filtering bugs by tags works fine in advanced search, the only problem is
that you can't combine it with filtering by releases (since that's broken
in advanced search and you have to use milestone page for that).
On Thu, Oct 9, 2014 at 12:18 PM, Dmitry Pyzhov wrote:
> We definitely need to assig
On 9 October 2014 07:49, henry hly wrote:
> Hi Joshua,
>
> ...in fact hierarchical scale
> depends on square of single child scale. If a single child can deal
> with 00's to 000's, cascading on it would then deal with 00,000's.
That is faulty logic - maybe the cascading solution needs to deal wit
On 8 October 2014 10:32, joehuang wrote:
> "maybe we should just slap a REST api on it". The challenge of Node-pool REST
> API is "What it will look like for these API, totally new API? current OS-API
> ?". From cloud operators' feed back, OS-API is preferred. If we developed
> totally new API
So so far, everyone seems really positive and psyched about the proposal.
It looks like providing some options for how to use would be best, that is
provide decorators and context managers.
Now the thing with the context manager, it can be as I stated:
with sql.reader() as session:
or
On 10/09/2014 09:31 AM, John Dennis wrote:
On 10/08/2014 04:58 PM, Adam Young wrote:
When gyee posted his X509 server-side auth plugin patch, the feedback
we gave was that it should be using the mapping code from Federation to
transform the environment variables set by the web server to the
Key
We definitely need to assign these bugs to the fuel-docs team. And there is
a good point from Alexandra Fedorova that commit message needs to have
enough information for tech writer. And reviewers should not merge fixes
that do not apply this rule. Otherwise we will end up with new bottlenecks.
On
Hello everyone,
Due to a number of issues discovered in the published Cinder 2014.2 RC1
(including two security issues), we generated a new Juno release
candidate. You can find the list of bugfixes in this RC and a link to a
source tarball at:
https://launchpad.net/cinder/juno/juno-rc2
Unless ne
On 10/9/14 1:31 PM, Chris Friesen wrote:
> On 10/09/2014 08:12 AM, Jeremy Stanley wrote:
> > On 2014-09-30 01:38:29 + (+), Jeremy Stanley wrote:
> > [...]
> >> the tips of these branches have been tagged "havana-eol" in
> >> preparation for branch deletion. The list of affected Git
> >> re
Hi all!
We've had one release critical bug discovered in the past week, and so
today an RC2 candidate was published. A tarball of that is available
at:
https://launchpad.net/ironic/+milestone/juno-rc2
This fixed the following bug:
Hash ring is stale after new conductor added
https://bugs.la
confirmed.
Note that we are making an exception here for a brand new parent.
I'd like to remind further candidate to use the proper "TC candidacy"
mail subject.
On 08/10/14 09:33 PM, Sean Dague wrote:
> I'd like to announce throwing my hat into the ring for the OpenStack
> Technical Committee.
>
confirmed.
Note that we are making an exception here for a brand new parent.
I'd like to remind further candidate to use the proper "TC candidacy"
mail subject.
On 08/10/14 09:33 PM, Sean Dague wrote:
> I'd like to announce throwing my hat into the ring for the OpenStack
> Technical Committee.
>
Hi,
I think it must be a mandatory request for fuel-library core reviewers.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Thu, Oct 9, 2014 at 10:19 AM, Mike Scherbakov
wrote:
> This discussion should go in the public, as not every developer is here,
> and other opinions ar
On 10/09/2014 08:12 AM, Jeremy Stanley wrote:
On 2014-09-30 01:38:29 + (+), Jeremy Stanley wrote:
[...]
the tips of these branches have been tagged "havana-eol" in
preparation for branch deletion. The list of affected Git
repositories is as follows:
openstack-dev/devstack
open
> The value it adds (and that an underscore would add in hvtype ->
> hv_type) is that the name would match the naming style for the vast
> majority of everything else in OpenStack. See, for examples:
Agreed.
> As mentioned in the review, I disagree on this point, since "doing a
> cleanup afterwar
Ah okay... That's seems to be perfect fine... Thank you! :-)
On 9 October 2014 10:22, Robert Li (baoli) wrote:
> Hi Thiago,
>
> A couple of things to consider:
> — As it is now, it doesn’t seem to be fully functional if you change
> your subnet to use SLAAC. The addresses that were assigne
Notes from the architecture review meeting on plugins UX:
- separate page for plugins management
- user installs the plugin on the master
- global master node configuration across all environments:
- user can see a list of plugins on Plugins tab (plugins description)
- Enable/
Thanks Lei for the reply and clarification.
So, instead of that we can use the following:
from keystone client.v2_0 import Client
keystone = Client(username=user, password=password, tenant_name=tenant,
auth_url=url)
with user, password, tenant and url can be obtained from cfg.CONF.
Thanks,
On 10/09/2014 09:45 AM, Murray, Paul (HP Cloud) wrote:
Hi All,
The following question relates to this change:
https://review.openstack.org/#/c/125091/
This change adds a field to the ComputeNode object called
“supported_instances”. It also adds an object called “SupportedInstance”
that has fie
On 10/09/2014 10:16 AM, Daniel P. Berrange wrote:
On Thu, Oct 09, 2014 at 01:45:43PM +, Murray, Paul (HP Cloud) wrote:
Hi All,
The following question relates to this change:
https://review.openstack.org/#/c/125091/
This change adds a field to the ComputeNode object called "supported_insta
On Thu, Oct 09, 2014 at 01:45:43PM +, Murray, Paul (HP Cloud) wrote:
> Hi All,
>
> The following question relates to this change:
>
> https://review.openstack.org/#/c/125091/
>
> This change adds a field to the ComputeNode object called
> "supported_instances". It also adds an object called
On 2014-09-30 01:38:29 + (+), Jeremy Stanley wrote:
[...]
> the tips of these branches have been tagged "havana-eol" in
> preparation for branch deletion. The list of affected Git
> repositories is as follows:
>
> openstack-dev/devstack
> openstack-dev/grenade
> openstack/ceilo
On 10/8/2014 9:21 PM, Joe Gordon wrote:
On Wed, Oct 8, 2014 at 6:12 PM, Michael Still mailto:mi...@stillhq.com>> wrote:
On Thu, Oct 9, 2014 at 11:58 AM, Joe Gordon mailto:joe.gord...@gmail.com>> wrote:
> On Wed, Oct 8, 2014 at 4:30 PM, Joe Gordon mailto:joe.gord...@gmail.com>> wrote
Hi All,
The following question relates to this change:
https://review.openstack.org/#/c/125091/
This change adds a field to the ComputeNode object called
"supported_instances". It also adds an object called "SupportedInstance" that
has fields called "arch", "hvtype" and "vm_mode".
All these n
Evgeniy,
Yes, the plugin management page should be a separate page. As for
dependency on releases, I meant that some plugin can work only on Ubuntu
for example, so for different releases different plugins could be available.
And please confirm that you also agree with the flow: the user install a
On 10/08/2014 04:58 PM, Adam Young wrote:
> When gyee posted his X509 server-side auth plugin patch, the feedback
> we gave was that it should be using the mapping code from Federation to
> transform the environment variables set by the web server to the
> Keystone userid, username, domain name
Hi Thiago,
A couple of things to consider:
― As it is now, it doesn’t seem to be fully functional if you change your
subnet to use SLAAC. The addresses that were assigned to your existing ports in
neutron wouldn’t be updated/changed. So basically, you can not simply make an
API call to change
Congrats :-D
On 9 October 2014 09:52, Thierry Carrez wrote:
> Hello everyone,
>
> One week to final release! Due to a number of issues discovered in the
> published Heat 2014.2 RC1, we generated a new Juno release candidate.
> You can find the list of bugfixes in this RC and a link to a sou
confirmed
On 09/10/14 09:07 AM, John Garbutt wrote:
> Hi,
>
> I would like to run for a seat on the Technical Committee, to help
> serve the whole OpenStack community during this time of change.
>
> I am employed by Rackspace, working on their public cloud. I am
> currently focus mostly on Nova.
Hi,
Vitaly, I like the idea of having separate page, but I'm not sure if it
should be on releases page.
Usually a plugin is not release specific, usually it's environment specific
and you can have
different set of plugins for different environments.
Also I don't think that we should enable plugin
Hi,
I would like to run for a seat on the Technical Committee, to help
serve the whole OpenStack community during this time of change.
I am employed by Rackspace, working on their public cloud. I am
currently focus mostly on Nova. I am nova-core, and currently nova's
blueprint czar. I am johnthet
On 10/08/2014 07:30 PM, Joe Gordon wrote:
> Recently there has been a lot of discussion around the development
> growing pains in nova. Instead of guessing about how bad some of the
> issues are, I tried to answer a few questions that may help us better
> understand the issues.
>
>
> Q: How many
Hello everyone,
One week to final release! Due to a number of issues discovered in the
published Heat 2014.2 RC1, we generated a new Juno release candidate.
You can find the list of bugfixes in this RC and a link to a source
tarball at:
https://launchpad.net/heat/juno/juno-rc2
Unless new release
Hi list,
Here is proposal previously posted on
https://bugs.launchpad.net/nova/+bug/1378233
It would be very useful for our case scenario to be able to have an
option that enables not counting suspended machines as consuming
resources. The use case is having little memory available and still
bein
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/10/14 01:55, Vasudevan, Swaminathan (PNB Roseville) wrote:
> Hi Folks,
>
>
>
> ./run_tests.sh fails to create the .venv with the latest neutron
> repo.
>
> It fails at MySQL-python.
>
> Does anyone know what is broken.
You probably miss l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/10/14 18:05, Mike Bayer wrote:
>
> On Oct 7, 2014, at 8:29 AM, Ihar Hrachyshka
> wrote:
>
>>
>> That said, I wonder how we're going to manage cases when those
>> *global* settings for the whole server should be really limited
>> to specifi
Let me propose another approach. I agree with most of Dmitry's statements
and it seems in MVP we need plugin management UI where we can enable
installed plugins. It should be a separate page. If you want to create
environment with a plugin, enable the plugin on this page and create a new
environmen
Hi
in nova/api/openstack/compute/views/images.py, there is a
function returns alternate links which contains project_id
However, I didn't see any info in glance API V2 spec
Can any one help me on :
1) what's the purpose of alternate link? can I remove the proje
On Wed, Oct 08, 2014 at 04:30:16PM -0700, Joe Gordon wrote:
> Recently there has been a lot of discussion around the development growing
> pains in nova. Instead of guessing about how bad some of the issues are, I
> tried to answer a few questions that may help us better understand the
> issues.
W
This discussion should go in the public, as not every developer is here,
and other opinions are important.
I believe that we are again diverting the conversation into a few
directions. Let's address things one by one, and feel free to spin off new
discussions out of this thread. After original ema
Hi Mike,
Great stuff! Fixing the mess with transactions and their scope is
probably one of the most important tasks for us, IMO. I look forward
for this to be implemented in oslo.db and consuming projects!
Thanks,
Roman
On Thu, Oct 9, 2014 at 12:07 AM, Mike Bayer wrote:
> Hi all -
>
> I’ve draf
On 10/09/2014 03:37 AM, Lei Zhang wrote:
> The question comes from my patch[1]. Kgriffs point that there are two
> way to get all the pools. But I don’t know which one is better, event
> though I comment that limit=0 is wired. I think there are three ways.
>
> use limit=0( current logical).
> pro:
64 matches
Mail list logo
