> -Original Message-
> From: Ian Cordasco [mailto:[email protected]]
> Sent: Friday, December 11, 2015 8:13 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog
> name for Glance Artifact
> -Original Message-
> From: McLellan, Steven
> Sent: Friday, December 11, 2015 6:37 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog
> name for Glance Artifact Repository API
>
> Hi Alex,
>
Hi All,
When I was looking at bugs related to race conditions of scheduler [1-3], it
feels like nova scheduler lacks sanity checks of schedule decisions according
to different situations. We cannot even make sure that some fixes successfully
mitigate race conditions to an acceptable scale. For
Hi,
I am wondering whether "domain" is a mapping to a real-world cloud tenant
(not the counterpart of "project" in v2 Identity API) because recently I
read a paper that describes "domain" as a fit for the abstract concept
"cloud tenant". Does this saying stay in line with community's purpose?
While I was trying to submit patches for projects that had old
keystoneclient references (distil was one of the projects), I noticed that
there hasn't been much action on this project [0]. It's been a year since a
commit [1], no releases [2], and I can't submit a patch since
the .gitreview file d
On 12/14/2015 10:01 AM, Steve Martinelli wrote:
While I was trying to submit patches for projects that had old
keystoneclient references (distil was one of the projects), I noticed
that there hasn't been much action on this project [0]. It's been a year
since a commit [1], no releases [2], and I
... and back to this thread after a few weeks :)
The conclusions I saw were:
* Audience for openstack-announce should be "users/non-dev"
* Service project releases announcements are good
* Client library release announcements good
* Security announcements are good
* Internal library (particularly
On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote:
>
>
> On 10 December 2015 at 04:35, Sandro Mathys wrote:
>>
>> On Thu, Dec 10, 2015 at 12:48 AM, Galo Navarro wrote:
>> > Hi,
>> >
>> >> I think the goal of this split is well explained by Sandro in the first
>> >> mails of the chain:
>> >>
>>
+1 It's really good job folks.
On Sat, Dec 12, 2015 at 2:25 AM, Vladimir Kuklin
wrote:
> Fuelers
>
> I am thrilled to announce that task based deployment engine [0] has been
> just merged into Fuel master. We checked it against existing BVT test cases
> for regressions as well as against functio
Vladimir,
Thanks for raising this question. I totally support idea of separating
provisioning and deployment steps. I believe it'll simplify a lot of
things.
However I have some comments regarding this topic, see them inline. :)
> For a package it is absolutely normal to throw a user dialog.
It
On 11/12, mtanino wrote:
> Hi Thang, Vincent,
>
> I guess the root cause is that finish_volume_migration() still
> handles a volume as a dictionary instead of volume object and
> the method returns dict volume.
>
> And then, 'rpcapi.delete_volume()' in migrate_volume_completion()
> tries to delet
Hi Fuelers,
I'd like to nominate Bulat Gaifulin [1] for
* fuel-web-core [2]
* fuel-mirror-core [3]
Bulat's doing a really good review with detailed feedback and he's a
regular participant in IRC. He's co-author of packetary and
fuel-mirror projects, and he made valuable contribution to fuel-web
Hi, Vladimir,
Please be informed that we'll have to also make an appropriate changes on
the fuel-agent side. But yes, it's possible to do it before SCF.
2015-12-11 20:05 GMT+03:00 Vladimir Kozhukalov :
> If there are no any objections, let's do fix fuel-menu ASAP. As Fedor said
> this approach w
Hi,
+1 from me to Bulat.
On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky
wrote:
> Hi Fuelers,
>
> I'd like to nominate Bulat Gaifulin [1] for
>
> * fuel-web-core [2]
> * fuel-mirror-core [3]
>
> Bulat's doing a really good review with detailed feedback and he's a
> regular participant in IRC. H
Marian Horban said on Thu, Dec 10, 2015 at 03:33:26PM +0200:
> Are there some progress with reloading configuration?
> Could we restore oslo-config review https://review.openstack.org/#/c/213062/
> ?
Hi Marian,
I'm also working on this, you might find
https://review.openstack.org/#/c/251471/ inte
Tox 2.3.1 was released on pypi a few minutes ago, and it fixes this issue.
Jordan
On Mon, Dec 14, 2015 at 12:55 AM, Robert Collins
wrote:
> On 13 December 2015 at 03:20, Yuriy Taraday wrote:
> > Tempest jobs in all our projects seem to become broken after tox 2.3.0
> > release yesterday. It's
Sean McGinnis wrote:
> On Thu, Dec 10, 2015 at 06:20:44PM +, Flavio Percoco wrote:
>>
>> With the new home for the release schedule, and it being a good place
>> for projects to add their own deadlines as well, I believe it would be
>> good for people that use calendars to have these .ics being
Tom Fifield wrote:
> ... and back to this thread after a few weeks :)
>
> The conclusions I saw were:
> * Audience for openstack-announce should be "users/non-dev"
> * Service project releases announcements are good
> * Client library release announcements good
> * Security announcements are good
Hi Tony,
Your reply gave me a hint that nova-consoleauth service must be running. I
did not start that service before so no token authentication was done. Now
after starting the service,
$nova get-serial-console vm-check-6
++-
Dmitry,
Q1. Yes.
> where do you plan to actually perform settings manipulation?
It was one of the critical blockers. Most of the settings are baked inside
fuel-library. Your feature [1] partially fixes this BTW. Which is good.
Partially, because only limited number of tasks has defined overrides
+1.
Aleksey Kasatkin
On Mon, Dec 14, 2015 at 12:49 PM, Vladimir Sharshov
wrote:
> Hi,
>
> +1 from me to Bulat.
>
> On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky
> wrote:
>
>> Hi Fuelers,
>>
>> I'd like to nominate Bulat Gaifulin [1] for
>>
>> * fuel-web-core [2]
>> * fuel-mirror-core [3]
>
Hi Fuelers,
As you might know, recently we moved to CentOS 7 and as a result we
got a small regression with PostgreSQL:
* Fuel 7 runs on CentOS 6.6 and uses manually built PostgreSQL 9.3.
* Fuel 8 runs on CentOS 7 and uses PostgreSQL 9.2 from CentOS upstream repos.
There are different opinions
Hi,
This is a reminder that we’ll have a team meeting today at #openstack-
meeting at 16.00 UTC.
Agenda:
- Review action items
- Current status (progress, issues, roadblocks, further plans)
- M-2 status and planning
- Open discussion
--
Best Regards,
Nikolay
__
+1
On Mon, Dec 14, 2015 at 3:05 PM, Aleksey Kasatkin
wrote:
> +1.
>
>
> Aleksey Kasatkin
>
>
> On Mon, Dec 14, 2015 at 12:49 PM, Vladimir Sharshov <
> [email protected]> wrote:
>
>> Hi,
>>
>> +1 from me to Bulat.
>>
>> On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky
>> wrote:
>>
>>> Hi Fue
On 14/12/15 19:33, Thierry Carrez wrote:
Tom Fifield wrote:
... and back to this thread after a few weeks :)
The conclusions I saw were:
* Audience for openstack-announce should be "users/non-dev"
* Service project releases announcements are good
* Client library release announcements good
* Se
On 2015-12-14 13:12, Igor Kalnitsky wrote:
> My opinion here is that I don't like that we're going to build and
> maintain one more custom package (just take a look at this patch [4]
> if you don't believe me), but I'd like to hear more opinion here.
>
> Thanks,
> Igor
>
> [1] https://bugs.launch
+openstack-dev
On 12/14/2015 02:40 PM, Dennis Dmitriev wrote:
> Hi All,
>
> We have updated the version of 'fuel-devops' framework to the 2.9.15.
>
> This is mainly bugfix update.
>
> Version 2.9.15 will be updated on our product CI during next several days.
>
> Changes since 2.9.13:
>
> - Process
Hi,
We have weekly Nova API meeting this week. The meeting is being held
Tuesday UTC1200.
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Please feel free to add items to the agenda.
Thanks
_
Hi,
The next meeting of the nova notification subteam will happen 2015-12-15
Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode
Agenda:
- Status of the outstanding specs and code reviews
- Subteam meeting during the vacation period
- AOB
See you there.
Cheers,
Gibi
[1] https://www
Hello!
Vote for update.
1. We have already shipped 9.3 in fuel-7.0. Downgrading such complicated
package without any reason is not good thing at all. User experience could
suffer a lot.
2. The next reason is tests. We have tested only 9.3, 9.2 was not tested at
all. I'm sure we could bring seriou
wasn't aware this project existed. i've contacted flwang.
just for reference, for those that extend Telemetry projects, it's good
to promote it here:
https://wiki.openstack.org/wiki/Telemetry#Externally_Managed
On 14/12/2015 4:09 AM, Andreas Jaeger wrote:
On 12/14/2015 10:01 AM, Steve Martin
Hi, Alexandre,
Yes, I think we need pass the version into `server_update` extension point.
My irc nick is alex_xu, let me know if you have any trouble with this.
Thanks
Alex
2015-12-13 2:34 GMT+08:00 Alexandre Levine :
> Hi all,
>
> os-user-data extension implements server_create method to add
> Meantime we can provide fuel-menu which will become a configuration
> gate for different subprojects. Perhaps we could consider to use
> pluggable approach, so each component will export plugin for fuel-menu
> with own settings.
fuel-menu could be a configuration gate for fuel deployment script
On 2015-12-14 12:18:07 +0100 (+0100), Jordan Pittier wrote:
> Tox 2.3.1 was released on pypi a few minutes ago, and it fixes
> this issue.
Thanks for testing it--I've gone ahead and unblocked our image
update automation.
If anyone notices new abnormalities from tox, please let the Infra
team know
On 2015-12-14 12:55:45 +1300 (+1300), Robert Collins wrote:
[...]
> my suggestion would be that we either make tox pip installed
> during jobs (across the board), so that we can in fact control it
> with upper-constraints,
That's a lot of added complication to deal with possible regressions
in ju
Hi,
> Downgrading for no reason could bring us to big trouble and bad user
experience
+1 to this. Let's keep PostgreSQL 9.3.
Regards,
Alex
On Mon, Dec 14, 2015 at 2:04 PM, Artem Silenkov
wrote:
> Hello!
>
> Vote for update.
>
> 1. We have already shipped 9.3 in fuel-7.0. Downgrading such comp
Hello!
Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC
in #openstack-meeting-4:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151215
See you there!
--
Emilien Macchi
signature.asc
Description: OpenPGP digital signature
__
Fuelers,
Since Mitaka OpenStack Infra has no resources to test python 2.6 support so the
corresponding jobs are not running anymore. Since Fuel master node is on CentOS
7 now, let’s drop Python 2.6 support in Fuel.
- romcheg
signature.asc
Description: Message signed with OpenPGP using GPGMai
Hi Li,
Sorry for the late reply. Unrelated point: please note that we've
moved the mailing lists to Openstack infra
([email protected] - I'm ccing the list here).
At the moment we don't support syncing the full Neutron DB, there has
been work done for this that would allow this u
+1
On Mon, Dec 14, 2015 at 3:05 PM, Roman Prykhodchenko wrote:
> Fuelers,
>
> Since Mitaka OpenStack Infra has no resources to test python 2.6 support
> so the corresponding jobs are not running anymore. Since Fuel master node
> is on CentOS 7 now, let’s drop Python 2.6 support in Fuel.
>
>
> -
Hi Roman,
We've discussed it [1], so +1
[1]
https://openstack.nimeyo.com/67521/openstack-dev-fuel-dropping-python2-6-compatibility
On Mon, Dec 14, 2015 at 5:05 PM, Roman Prykhodchenko wrote:
> Fuelers,
>
> Since Mitaka OpenStack Infra has no resources to test python 2.6 support
> so the corres
Sorry for duplicating discussions. os-dev subsription was broken for me for a
while so I missed a lot :(
> 14 груд. 2015 р. о 15:23 Evgeniy L написав(ла):
>
> Hi Roman,
>
> We've discussed it [1], so +1
>
> [1]
> https://openstack.nimeyo.com/67521/openstack-dev-fuel-dropping-python2-6-compat
Hi all,
In the big tent, project teams are expected to maintain their own
install guides within their projects' source tree. There's a
conversation going on over in the docs list[1] about changing this, but
in the meantime...
Ironic (and presumably other projects) publish versioned documentation,
On 12/14/2015 03:42 PM, Jim Rollenhagen wrote:
Hi all,
In the big tent, project teams are expected to maintain their own
install guides within their projects' source tree. There's a
conversation going on over in the docs list[1] about changing this, but
in the meantime...
Ironic (and presumably
Hi everyone,
I have a change submitted that lays the groundwork for using custom enums and
fields that are used by versioned objects [1]. These custom fields allow for
verification on a set of valid values, which prevents the field from being
mistakenly set to something invalid. These custom fi
> One of potential disadvantages is that it is harder to track package
> dependencies, but I think
> a deployment script should be a root of the package dependency tree.
That's something I'd try to avoid. Let's be close to distro upstream
practice. I never saw something like "fuel-deploy" that ru
On Mon, Dec 14, 2015 at 6:34 PM, Sandro Mathys wrote:
> On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote:
>>
> Honestly, I don't think this discussion is leading anywhere.
> Therefore, I'd like to request a decision by the MidoNet PTL as per
> [1].
I apologize for jumping in a bit late. Clea
On 12/14/2015 08:20 AM, Cheng, Yingxin wrote:
> Hi All,
>
>
>
> When I was looking at bugs related to race conditions of scheduler
> [1-3], it feels like nova scheduler lacks sanity checks of schedule
> decisions according to different situations. We cannot even make sure
> that some fixes succ
On 12/11/2015 08:51 PM, Alexander Tivelkov wrote:
Hi Steve,
Thanks for the note on port. Any objections on glare using 9494 then?
Anyone?
Yes, I object to 9494. There should be no need to use any custom port
for Glare's API service. Just use 80/443, which are HTTP(S)'s standard
ports. It was
On 12/11/2015 08:25 PM, Alexander Tivelkov wrote:
Hi folks!
As it was decided during the Mitaka design summit, we are separating the
experimental Artifact Repository API from the main Glance API. This API
will have a versioning sequence independent from the main Glance API and
will be run as a s
On 12/14/15, 02:18, "Kuvaja, Erno" wrote:
>> -Original Message-
>> From: McLellan, Steven
>> Sent: Friday, December 11, 2015 6:37 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service
>>Catalog
>> nam
On Mon, Dec 14, 2015 at 9:28 AM, Ian Cordasco
wrote:
>
>
> On 12/14/15, 02:18, "Kuvaja, Erno" wrote:
>
> >> -Original Message-
> >> From: McLellan, Steven
> >> Sent: Friday, December 11, 2015 6:37 PM
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> Subject: Re:
The port binding issues are usually related to a neutron physical interface
mapping issue however based on your previous config I don't think that was the
problem. If you're deploying Liberty/Master(Mitaka) there was was a fix that
went in that resolved an issue within neutron and the use of L2/
On Tue, Dec 15, 2015 at 12:02 AM, Ryu Ishimoto wrote:
> On Mon, Dec 14, 2015 at 6:34 PM, Sandro Mathys wrote:
>> On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote:
>>>
>> Honestly, I don't think this discussion is leading anywhere.
>> Therefore, I'd like to request a decision by the MidoNet PT
Hi Nick,
We have already designed the data sync feature[1], but this
development was suspended temporarily in favor of completing the v5.0
development of MidoNet.
We will be resuming development work on this project soon (with high priority).
It sounds to me like you need a completed, mature too
Thanks. So it looks like os_volume-attachments has now been linked
into the 2.1 doc. The lack of documentation for the PUT / update
attachment doc was also noted on the etherpad. So my only remaining
questions revolve around the dual and differing API implementations of
the read volume attachmen
FYI it looks like Ansible Fest London is Feb 18th.
On Thu, Dec 10, 2015 at 1:29 PM, Amy Marrich wrote:
> I'd be game to join in if it's in San Antonio. While I'd love to go to
> London I don't think I'd make.
>
> Like Major I'd like to see some doc work.
>
> Amy Marrich
>
On Tue, Dec 15, 2015 at 1:00 AM, Sandro Mathys wrote:
> On Tue, Dec 15, 2015 at 12:02 AM, Ryu Ishimoto wrote:
>
> So if I understand you correctly, you suggest:
> 1) the (midonet/internal) low level API stays where it is and will
> still be called python-midonetclient.
> 2) the (neutron/external)
On Mon, Dec 14, 2015 at 6:28 AM, Tom Fifield wrote:
> On 14/12/15 19:33, Thierry Carrez wrote:
>
>> Tom Fifield wrote:
>
> * Do SDK releases fit on -announce?
>>>
>>
>> I guess they could -- how many of those are we expecting ?
>>
>>
> So far it looks close to zero emails :) PythonSDK is the only
Swami,
Thanks for doing this. I'll continue to increase my attention to DVR
reviews. This will help.
Carl
On Fri, Dec 11, 2015 at 4:23 PM, Vasudevan, Swaminathan (PNB
Roseville) wrote:
> Hi Armando/Carl,
>
> Yes based on Carl’s recommendation I have categorized the bugs in the Wiki
> below ri
Hi,
Thank you guys to join us today!
Meeting minutes -
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-14-16.01.html
Meeting full log -
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-14-16.01.log.html
Best Regards,
Nikolay
__
I am using the liberty branch. Unfortunately this did not help, I get
the same error.
I also don't understand where the neutron service should run. This is
the output on my compute node:
root@os-compute-1:~# ps aux | grep neutron
root 18782 0.0 0.0 11748 2232 pts/0S+ 17:56 0:00 gr
+1
I think it is good compromise. Thanks Ryu!
I understand the CLI will belong to the external part. I much prefer to have
it in a separate project rather than into the plugin. Even if the code is
tiny.
If you will want to just do midonet calls for debugging or check the MidoNet
virtual infrastr
Thank you for the explanation, Gorka!
Mitsuhiro
On 12/14/2015 05:00 AM, Gorka Eguileor wrote:
On 11/12, mtanino wrote:
Hi Thang, Vincent,
I guess the root cause is that finish_volume_migration() still
handles a volume as a dictionary instead of volume object and
the method returns dict volume
Hello,
Please could you backport the following commit:
2d983e20b0015ed685a874bb6117261dc1af5661
to the puppet-cinder Kilo branch?
Thank you
--
Christopher Brown
__
OpenStack Development Mailing List (not for usage questio
On 10/12/15 14:42, Sean Dague wrote:
> On 12/02/2015 12:37 PM, Rosa, Andrea (HP Cloud Services) wrote:
>> Hi
>>
>> thanks Sean for bringing this point, I have been working on the change and
>> on the (abandoned) spec.
>> I'll try here to summarize all the discussions we had and what we decided.
On 10/12/15 15:29, Matt Riedemann wrote:
>> In a simplified view of a detach volume we can say that the nova code
>> does:
>> 1 detach the volume from the instance
>> 2 Inform cinder about the detach and call the terminate_connection on
>> the cinder API.
>> 3 delete the dbm recod in the nova DB
On 13 December 2015 at 23:01, Kevin Benton wrote:
> Yes, as I'm starting to understand the use case, I think it would actually
> make more sense to add an AZ-network mapping table. Then whatever
> implementation can populate them based on the criteria it is using
> (reference would just do it on
Hi folks,
Something snuck in past the gate last night [1]. Please stop rechecking and
pushing in the merge queue until the matter is resolved.
I will follow up with details, if someone knows more, please find me on IRC.
Thanks,
Armando
[1]
http://logs.openstack.org/00/254900/4/gate/gate-grenade
What about the case where your not running ha routers? Should you still run
more then one?
Thanks,
Kevin
From: Assaf Muller [[email protected]]
Sent: Saturday, December 12, 2015 12:44 PM
To: OpenStack Development Mailing List (not for usage questions)
Sub
On Mon, Dec 14, 2015 at 6:07 PM, Jaume Devesa wrote:
> +1
>
> I think it is good compromise. Thanks Ryu!
>
> I understand the CLI will belong to the external part. I much prefer to
> have
> it in a separate project rather than into the plugin. Even if the code is
> tiny.
>
Let me summarize it:
On 12/14/2015 12:32 PM, Armando M. wrote:
> Hi folks,
>
> Something snuck in past the gate last night [1]. Please stop rechecking
> and pushing in the merge queue until the matter is resolved.
>
> I will follow up with details, if someone knows more, please find me on IRC.
>
> Thanks,
> Armando
On 14 December 2015 at 09:51, Sean Dague wrote:
> On 12/14/2015 12:32 PM, Armando M. wrote:
> > Hi folks,
> >
> > Something snuck in past the gate last night [1]. Please stop rechecking
> > and pushing in the merge queue until the matter is resolved.
> >
> > I will follow up with details, if some
Prathyusha Guduri wrote on 12/11/2015
06:37:02 AM:
> From: Prathyusha Guduri
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 12/11/2015 06:39 AM
> Subject: [openstack-dev] [nova][serial-console-proxy]
>
> Hi All,
> I have set up open stack on an Arm64 machine
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday December 15th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting
Anyone is welcome to to add agend
Thanks Sean!
On Mon, Dec 14, 2015 at 12:58 PM Armando M. wrote:
> On 14 December 2015 at 09:51, Sean Dague wrote:
>
>> On 12/14/2015 12:32 PM, Armando M. wrote:
>> > Hi folks,
>> >
>> > Something snuck in past the gate last night [1]. Please stop rechecking
>> > and pushing in the merge queue u
Howdy Kuryr developers!
Like other OpenStack projects, I've added the functionality to use release
notes with Kuryr. Once [1] merges, we can add release notes in the
"releasenotes/notes" directory. I encourage everyone who has added a
feature item to Kuryr to please add a release note for that fea
On 14 December 2015 at 10:18, Paul Michali wrote:
> Thanks Sean!
>
> On Mon, Dec 14, 2015 at 12:58 PM Armando M. wrote:
>
>> On 14 December 2015 at 09:51, Sean Dague wrote:
>>
>>> On 12/14/2015 12:32 PM, Armando M. wrote:
>>> > Hi folks,
>>> >
>>> > Something snuck in past the gate last night [
Nice job on this. Looking forward to reaping the benefits of the stable
branch stuff for our upgrades testing too.
Dan
On Fri, 2015-12-11 at 12:35 +, Steven Hardy wrote:
> Hi all,
>
> So, after the painful process of getting CI working for
> stable/liberty,
> everything is now working pretty
On Fri, 2015-12-11 at 21:50 +0100, Jaume Devesa wrote:
> Hi all,
>
> Today TripleO CI jobs failed because a new commit introduced on
> puppetlabs-mysql[1].
> Mr. Jiri Stransky solved it as a temporally fix by pinning the puppet
> module clone to a previous
> commit in the tripleo-common project[2
On 11/25/2015 11:05 PM, Assaf Muller wrote:
We could then consider running the script automatically on a daily
basis and publishing the
resulting URL in a nice bookmarkable place.
An update on this. The easiest bookmarkable place that I found it's my
blog [1]. I have a script that updates th
Hi,
If we can stick with upstream PostgresSQL that would be really nice.
Otherwise security updates and regular package update will be a burden of
package maintainers. Ideally we should have as less forked packages as
possible.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On M
This is a gentle reminder that the downtime will be this Wednesday
starting at 17:00 UTC.
Thank you for your patience,
Spencer
--
Spencer Krum
[email protected]
On Tue, Dec 1, 2015, at 10:19 PM, Stefano Maffulli wrote:
> On 12/01/2015 06:38 PM, Spencer Krum wrote:
> > There is a thread b
It's important to note that given the change in the upgrade method, there
will be no actual downgrade of the package, since Fuel 8.0 Admin Node will
be installed on a clean system. So, from the upgrade standpoint I see no
obstacles to have 9.2 in Fuel 8.0. I also greet any chance to reduce the
numb
Hi Steve,
Thanks for the heads up. I just worked this out with AJaejer. The
.gitreview file has been updated and we will disable the CI job
temporarily. Please let me know if there is any question. Cheers.
On 14/12/15 22:01, Steve Martinelli wrote:
>
> While I was trying to submit patches for pr
Hi neutrinos,
A kind reminder for this week's meeting.
For this week we'll continue with the post-milestone format: we'll continue
talking about blueprints/specs and RFEs. We'll be brief on announcements
and bugs, and skip the other sections, docs and open agenda. More details
on [1].
Also, plea
Hi,
We are overjoyed to present this week's subteam report for Ironic. As
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
(diff with Dec 7)
- Open: 179 (+4). 16 new (+4), 58 in progress (-3), 0 critical (-1), 13
high (-3) and 9 incomplet
The neutron service is running on the physical host within the compute
nodes, as well as the l3 agent containers. You should be able to do
`service neutron-linuxbridge-agent restart` on the compute node to start
the service. If its failing to run, there should be something within the
logs to in
Hi Christopher!
On 12/14/2015 12:18 PM, Christopher Brown wrote:
> Hello,
>
> Please could you backport the following commit:
>
> 2d983e20b0015ed685a874bb6117261dc1af5661
>
> to the puppet-cinder Kilo branch?
Sure, this is something I just did for you:
https://review.openstack.org/#/c/257565/
> Thanks for summing this up, Deva. The planned solution still gets my
> vote; we build that, deprecate the old single compute host model where
> nova handles all scheduling, and in the meantime figure out the gaps
> that operators need filled and the best way to fill them.
Mine as well, speaking
Hi all,
The Kosmos mid cycle has been set for the HPE Offices, in Seattle WA [0]
from the 20th to the 22nd of January.
If you are interested in attending please fill out [1]
so I can make sure the rooms are big enough.
We are tracking ideas for the 3 days here [0] - please put any ideas
you have
Hi all,
The Designate mid cycle has been set for the HPE Offices, in Galway,
Ireland [0] from the 08th to the 10th of February.
If you are interested in attending please fill out [1]
so I can make sure the rooms are big enough.
We are tracking ideas for the 3 days here [0] - please put any ideas
Hi All,
I had a few issues/questions regarding the statuses (provisioning_status
and operating_status) of a v2 LoadBalancer. To preface these, I am working
on the LBaaS v2 support in Heat.
The first question regards the allowed values for each of
provisioning_status and operating status. Here i
Unfortunately, "tenancy" has multiple definitions in our world so let me
try to clarify further! Do you have a link to that paper?
Tenants (v2) and projects (v3) have a history as serving to isolate the
resources (VMs, networks, etc) of multiple tenants. They literally provide
for multitenancy.
D
If you're not running HA routers, you have a couple of options that
I'm aware of:
1) Use multiple L3 agents in A/A, and enable
neutron.conf:allow_automatic_l3agent_failover. In which case you'd
enable the metadata agent on each node. There's pros and cons of this
approach vs. HA routers. Significa
A question but what filtering/scheduling would be done in which place;
any thoughts on the breakup between nova and ironic?
If say ironic knows about all baremetal resources and nova doesn't know
about them, then what kind of decisions can nova make during scheduling
time? I guess the same que
ha and dvr don't play nicely today though, and for our use case, if given the
choice, dvr looks more appealing then l3-ha. Thanks for the advice. We may just
go with the pacemaker option with dvr taking most of the load off of the
network node until l3+ha & dvr all play nice.
Thanks,
Kevin
On Mon, Dec 14, 2015 at 06:42:13AM -0800, Jim Rollenhagen wrote:
> Hi all,
>
> In the big tent, project teams are expected to maintain their own
> install guides within their projects' source tree. There's a
> conversation going on over in the docs list[1] about changing this, but
> in the meantim
I'm very much against it.
In my environment we're going to be depending heavily on the nova
scheduler for affinity/anti-affinity of physical datacenter constructs,
TOR, Power, etc. Like other operators we need to also have a concept of
host aggregates and availability zones for our baremetal as w
Hi Bryan,
On Mon, 2015-12-14 at 15:19 -0600, Bryan Jones wrote:
> Hi All,
>
> I had a few issues/questions regarding the statuses
> (provisioning_status and operating_status) of a v2 LoadBalancer. To
> preface these, I am working on the LBaaS v2 support in Heat.
>
> The first question regards th
1 - 100 of 117 matches
Mail list logo
