Hi,
At any rate, would be great to know, and if there isn't a strong reason
against it we can make project name 255 for some more flexibility.
Plus although there is no true official standard, most projects in
OpenStack seem to use 255 as the default for a lot of string fields.
Weirdly enough,
HI,
Did you configured everything according to
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking?
( including intel_iommu=on ) ?
Can you attach more logs and config files of the nova/neutron/neutron plugins
Are you working with devstack or distro?
From: Murali B [mailto:mbi...@gm
Thierry Carrez wrote:
> A new release candidate for horizon for the end of the Newton cycle was
> generated, to catch release-critical fixes and include recent
> translations. You can find the source code tarball at:
>
> [...]
Woops, missing link:
https://tarballs.openstack.org/horizon/horizon-10
Hello everyone,
A new release candidate for mistral for the end of the Newton cycle was
generated, to catch release-critical fixes. You can find the source code
tarball at:
https://tarballs.openstack.org/mistral/mistral-3.0.0.0rc2.tar.gz
Unless new release-critical issues are found that warrant
Hello everyone,
A new release candidate for neutron for the end of the Newton cycle was
generated, to catch release-critical fixes and update to the latest
available translations. You can find the source code tarball at:
https://tarballs.openstack.org/neutron/neutron-9.0.0.0rc3.tar.gz
Unless new
Hello everyone,
I am having a problem writing/updating a test case to verify some new
feature (in my case, the "description" field for a network).
Acoording to Tempest Coding Guide[1], I am supposed to check if the
related feature is there by @test.requires_ext() like this:
@test.requires_ex
Ok, next meeting is canceled.
On Wed, Sep 28, 2016 at 6:12 PM, Vitaly Gridnev
wrote:
> Hi team,
>
> Since all of us are preparing for future summit and there is no specific
> topics to cover, I think that we should skip meeting tomorrow at Sept 29.
> If there is topic to discuss, please write em
Hi
I am trying to execute the lbaas db upgrade procedure but I have several
question regarding this.
>From the patch:
I moved to /neutron-lbaas/neutron_lbaas/db/migration
- Create a revision file
I executed "neutron-db-manage revision -m "description of revision"
--autogenerate"
At this poin
Hi,
There are certainly exist a bug in stackalytics [1]. Current contribution
to different openstack/* projects was counted for deb-* . Now all affected
commit records on stackalytics are removed from deb-* projects, but they
should be moved to proper non-deb projects. Is there any one how could
út 27. 9. 2016 v 18:21 odesílatel Timur Nurlygayanov <
tnurlygaya...@mirantis.com> napsal:
> Hi milan,
>
> we have measured the test coverage for OpenStack components with
> coverage.py tool [1]. It is very easy tool and it allows measure the
> coverage by lines of code and etc. (several metrics a
út 27. 9. 2016 v 20:12 odesílatel Assaf Muller napsal:
> On Tue, Sep 27, 2016 at 2:05 PM, Assaf Muller wrote:
>
>>
>>
>> On Tue, Sep 27, 2016 at 12:18 PM, Timur Nurlygayanov <
>> tnurlygaya...@mirantis.com> wrote:
>>
>>> Hi milan,
>>>
>>> we have measured the test coverage for OpenStack componen
> On 29 Sep 2016, at 06:26, Steven Dake (stdake) wrote:
>
> If you have a different parsing of the deprecation policy, feel free to chime
> in.
Heka is only used as an internal component of Kolla and is not provided as a
service for the operators. It should be sufficient to replace Heka by som
On 28/09/16 20:59 +0100, Chris Dent wrote:
On Wed, 28 Sep 2016, Jim Rollenhagen wrote:
+1 to release notes or something of that like. i was asked to give an
update on the TC internally and it seems the only information out there
is to read through backlog of meeting logs or track the items that
út 27. 9. 2016 v 18:05 odesílatel Doug Hellmann
napsal:
> Excerpts from milanisko k's message of 2016-09-27 12:30:09 +:
> > Hello Stackers!
> >
> > The ironic inspector project keeps track of introspection finished_at
> time
> > stamps.
> > We're just discussing how to reasonably query time r
On 28/09/16 17:49 -0400, Ryan Hallisey wrote:
Hey Flavio,
I attached two architecture diagrams highlighting the four main
lifecycle pieces of OpenStack orchestration: bootstrapping,
deployment, upgrading, and scaling. Config is also in there, but
it was constant throughout each diagram.
The dia
Hi all,
there is a patch for neutron that switches neutron policy engine from
passing context.to_dict() into oslo.policy to using
context.to_policy_values() that was added recently to oslo.context.
The patch is: https://review.openstack.org/#/c/370499/
The new function from oslo.context re
Thierry Carrez wrote:
> Hello everyone,
>
> A new release candidate for mistral for the end of the Newton cycle was
> generated, to catch release-critical fixes. You can find the source code
> tarball at:
>
> https://tarballs.openstack.org/mistral/mistral-3.0.0.0rc2.tar.gz
Actually there was a c
Hello everyone,
We have a non-voting multinode grenade job in check queue for around a
month now.
https://goo.gl/Kr10s6
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists
On 09/29/2016 12:10 PM, Michał Dulko wrote:
> Hello everyone,
>
> We have a non-voting multinode grenade job in check queue for around a
> month now.
>
> https://goo.gl/Kr10s6
Whoops, I've sent this by mistake. Here's the actual email:
Hello everyone,
We have a non-voting multinode grenade job i
On Thu, Sep 29, 2016 at 5:27 AM, milanisko k wrote:
>
>
> út 27. 9. 2016 v 20:12 odesílatel Assaf Muller napsal:
>
>> On Tue, Sep 27, 2016 at 2:05 PM, Assaf Muller wrote:
>>
>>>
>>>
>>> On Tue, Sep 27, 2016 at 12:18 PM, Timur Nurlygayanov <
>>> tnurlygaya...@mirantis.com> wrote:
>>>
Hi mil
On Thu, 29 Sep 2016, Flavio Percoco wrote:
I'm not saying it wouldn't be useful at all. What I'm saying is that
the format, and more importantly, the content will have to be studied.
I'll likely start working on this and I could use your help whether or
not you'll win the election
:)
Yeah, tha
2016-09-26 16:05 GMT+02:00 Anita Kuno :
> On 16-09-26 07:48 AM, Haïkel wrote:
>>
>> Hi,
>>
>> following our discussions about 3rd party gates in RPM packaging project,
>> I suggest that we vote in order to promote the following gates as voting:
>> - MOS CI
>> - SUSE CI
>>
>> After promotion, all pa
Hello, all.
Due to the local holidays, I have to cancel the Dragonflow weekly meeting
on Monday.
The following meeting on the 12th Oct. is planned to take place as usual.
Thank you,
Omer Anson.
__
OpenStack Development Mailin
Also, here’s the pointer to the latest guide which had been updated in this
last cycle: http://docs.openstack.org/draft/networking-guide/config-sriov.html
Which release are you using ?
What is the content of your neutron ml2_conf.ini file ?
/ludovic
From: Lenny Verkhovsky [mailto:len...@mellan
Murali,
I have seen this binding error once when I failed to configure the SRIOV agent.
Please check the agent settings
as per the link below that Lenny sent.
Thanks
Prasanth
- Original Message -
From: "Lenny Verkhovsky"
To: "OpenStack Development Mailing List (not for usage questions)
On 16-09-29 08:12 AM, Haïkel wrote:
2016-09-26 16:05 GMT+02:00 Anita Kuno :
On 16-09-26 07:48 AM, Haïkel wrote:
Hi,
following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS CI
- SUSE CI
After prom
On Thu, Sep 29, 2016 at 03:49:27PM +0800, Bruce Tan wrote:
> Hello everyone,
>
> I am having a problem writing/updating a test case to verify some new
> feature (in my case, the "description" field for a network).
>
> Acoording to Tempest Coding Guide[1], I am supposed to check if the
> related f
Hi,
2016-09-29 14:12 GMT+02:00 Haïkel :
> Gates that do not leave verified +1 are called non-voting, so
> logically gates that leaves verified +1 are called voting gates.
+1
Greetings,
Dirk
__
OpenStack Development Mailin
Hi Andreas,
Because you asked so nicely, tada:
http://docs.openstack.org/project-install-guide/baremetal/newton/
Also, thanks for clarifying about ../draft/.. !
--ruby
From: Andreas Jaeger
Organization: SUSE Linux GmbH, Nuernberg, GF: Felix Imendörffer, Jane Smithard,
Graham Norton , HRB 212
Hi Ken,
I am guessing the above "restart nodes" is for verifying each
> OpenStack service restarts successfully, right?
Yes, this is right. And we also will check that HA logic for these
services works correctly (for example, rescheduling of L3 Neutron
agents for networks).
But these service scr
+1
It seems good!
On Thu, Sep 29, 2016 at 7:25 AM, Michał Dulko
wrote:
> On 09/29/2016 12:10 PM, Michał Dulko wrote:
> > Hello everyone,
> >
> > We have a non-voting multinode grenade job in check queue for around a
> > month now.
> >
> > https://goo.gl/Kr10s6
>
> Whoops, I've sent this by mist
On 2016-09-29 15:10, Ruby Loo wrote:
> Hi Andreas,
>
>
>
> Because you asked so nicely, tada:
> http://docs.openstack.org/project-install-guide/baremetal/newton/
Great, thanks a lot Ruby and Ironic team!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX G
Hi,
>> Gates that do not leave verified +1 are called non-voting, so
>> logically gates that leaves verified +1 are called voting gates.
> +1
Eh, what I wanted to +1 was:
+1 to promote the check jobs on rpm-packaging from MOS and SUSE CI as
voting jobs.
Sorry for mixing up definitions and then
We are psyched to announce the release of:
openstack-doc-tools 1.2.0: Tools for OpenStack Documentation
With source available at:
http://git.openstack.org/cgit/openstack/openstack-doc-tools
Please report issues through launchpad:
http://bugs.launchpad.net/openstack-manuals
For more de
Roman,
There are certainly exist a bug in stackalytics [1]. Current contribution
> to different openstack/* projects was counted for deb-* . Now all affected
> commit records on stackalytics are removed from deb-* projects, but they
> should be moved to proper non-deb projects. Is there any one
Folks,
3 incumbents are not running. Many thanks to Russell, Anne, Kyle for
their service and dedication (per TC meeting logs -
http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-09-27-20.01.log.html)
9 candidates are running (per
https://review.openstack.org/#/q/project:openstack/election).
Good news forcontributorfrom China, will attend the meeting.
Thanks,
Zhu Rong__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://li
On 9/19/2016 2:49 PM, Armando M. wrote:
I asked an extra session on the Neutron side to dedicate to
nova/neutron, and I was hoping to have them back to back, but it doesn't
look possible under the current arrangement. Do you think it's worth
trying and tweak things? If not I guess we can have o
Hello everyone,
The release candidate for Senlin for the end of the Newton cycle is
available! You can find the RC2 source code tarball at:
https://tarballs.openstack.org/senlin/senlin-2.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this RC2 wi
Hello everyone,
The release candidate for searchlight for the end of the Newton cycle
is available! You can find the RC2 source code tarball at:
https://tarballs.openstack.org/searchlight/searchlight-1.0.0.0rc2.tar.gz
https://tarballs.openstack.org/searchlight-ui/searchlight-ui-1.0.0.0rc2.tar.gz
Agree with Christian, this is our internal wiring. As long as we
provide automated upgrade procedure which will seamlessly migrate from
heka to alternative we want, we should be good without deprecation per
se.
Cheers,
Michal
On 29 September 2016 at 04:36, Christian Berendt
wrote:
>> On 29 Sep 2
We are happy to announce the release of:
networking-hyperv 3.0.0: This project tracks the work to integrate the
Hyper-V networking with Neutron. This project contains the Hyper-V
Neutron Agent Mixin, Security Groups Driver, ML2 Mechanism Driver and
the utils modules they use in order to properly b
Tagging kolla
On 29/09/16 16:22, Michał Jastrzębski wrote:
Agree with Christian, this is our internal wiring. As long as we
provide automated upgrade procedure which will seamlessly migrate from
heka to alternative we want, we should be good without deprecation per
se.
Cheers,
Michal
On 29 Sep
So I requested for TripleO RC2 release:
https://review.openstack.org/#/c/378620/
Once this patch will merge, we'll have stable/newton on:
- openstack/instack-undercloud
- openstack/puppet-tripleo
- openstack/tripleo-common
- openstack/tripleo-heat-templates
- openstack/tripleo-puppet-elements
- op
On Sep 29, 2016 3:06 PM, "Christian Berendt"
wrote:
>
> > On 29 Sep 2016, at 06:26, Steven Dake (stdake) wrote:
> >
> > If you have a different parsing of the deprecation policy, feel free to
chime in.
>
> Heka is only used as an internal component of Kolla and is not provided
as a service for th
The agenda [0] is empty again this week so the meeting is closed, see you
again next week
[0] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
--
Andrew Woodward
Mirantis
__
OpenStack Development Mailing List (not
notification = of course
relase note with information and upgrade info = of course
1 full release of supporting both heka and alternative = not so much
On 29 September 2016 at 10:54, Swapnil Kulkarni (coolsvap)
wrote:
> On Sep 29, 2016 3:06 PM, "Christian Berendt"
> wrote:
>>
>> > On 29 Sep 2016
Hi, Juan -
Actually, the third option is also not an option in the current undercloud
> setup, since making the services listen in 0.0.0.0 will break HAProxy. So
> when you're deploying with TLS things will break since we use HAProxy to
> terminate TLS connections.
>
Ah, that's correct, isn't it.
On 9/27/16, 8:23 AM, "Jim Rollenhagen" wrote:
On Tue, Sep 27, 2016 at 9:57 AM, Loo, Ruby wrote:
> Hi Yuriy,
>
>
>
> Thanks for bringing this up. I'm good with your list, with the exception
of
> driver_info and instance_info. I'm on the fence with these two. If we
Excerpts from milanisko k's message of 2016-09-29 09:48:40 +:
> út 27. 9. 2016 v 18:05 odesílatel Doug Hellmann
> napsal:
>
> > Excerpts from milanisko k's message of 2016-09-27 12:30:09 +:
> > > Hello Stackers!
> > >
> > > The ironic inspector project keeps track of introspection finishe
On Sep 29, 2016 9:30 PM, "Michał Jastrzębski" wrote:
>
> notification = of course
> relase note with information and upgrade info = of course
> 1 full release of supporting both heka and alternative = not so much
>
> On 29 September 2016 at 10:54, Swapnil Kulkarni (coolsvap)
> wrote:
> > On Sep 2
+1. I think it would be beneficial to get more eyes on our testing as well
On Wed, Sep 28, 2016 at 10:15 AM, Iury Gregory wrote:
> +1 from me, David is doing an awesome job in p-o-i =)
>
> 2016-09-28 13:08 GMT-03:00 Rich Megginson :
>>
>> On 09/28/2016 10:06 AM, Emilien Macchi wrote:
>>>
>>> Unt
Great, I proposed the change here: https://review.openstack.org/#/c/379583/
Thanks for your feedback!
On Thu, Sep 29, 2016 at 12:18 PM, Alex Schultz wrote:
> +1. I think it would be beneficial to get more eyes on our testing as well
>
> On Wed, Sep 28, 2016 at 10:15 AM, Iury Gregory wrote:
>>
On Thu, 2016-09-29 at 12:07 -0400, Doug Hellmann wrote:
> Excerpts from milanisko k's message of 2016-09-29 09:48:40 +:
[snip]
> > > Doug, I'm afraid that dateutil.parser.parse doesn't support intervals
> > either: http://paste.openstack.org/show/583452/
> > Is there any interest in oslo_utils.
On Tue, Sep 27 2016, milanisko k wrote:
> I'd like to ask whether other projects need to parse time intervals and/or
> how do they achieve that.
We kind of do that in Gnocchi, but we do with 2 fields: one ISO8601
timestamp and a timestamp field, which we parse using pytimeparse, you
(can check gn
On Mon, Sep 26 2016, Eric K wrote:
> On a fresh devstack install with ceilometer clients version 2.6.1,
> client.alarms.list() errors when other things (like client.events.list())
> succeeds.
Do you have Aodh installed?
Why not switching to aodhclient?
--
Julien Danjou
;; Free Software hacker
;
Hello everyone,
The release candidate for Tripleo for the end of the Newton cycle is
available! You can find the RC2 source code tarballs at:
https://tarballs.openstack.org/instack-undercloud/instack-undercloud-5.0.0.0rc2.tar.gz
https://tarballs.openstack.org/puppet-tripleo/puppet-tripleo-5.2.0.t
On Thu, Sep 29, 2016 at 1:10 PM, Davanum Srinivas wrote:
> Hello everyone,
>
> The release candidate for Tripleo for the end of the Newton cycle is
> available! You can find the RC2 source code tarballs at:
>
> https://tarballs.openstack.org/instack-undercloud/instack-undercloud-5.0.0.0rc2.tar.gz
Hello everyone,
The release candidate for OpenStack-Ansible for the end of the Newton
cycle is available! You can find the details at:
https://releases.openstack.org/newton/index.html#newton-openstack-ansible
Unless release-critical issues are found that warrant a release
candidate respin, this
Hey,
Great -- thanks everyone. Let's keep on rocking.
Sometimes, it works outside of Devstack. Let's keep it that way :)
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Thu, Sep 29, 2016 at 12:33 PM, Emilien Macchi wrote:
> Great, I proposed t
Focus
-
This is the final release week. We're almost there!
Most project teams should be preparing for the summit in Barcelona.
General Notes
-
The release management team will tag the final Newton release on 6
October (project teams do not need to take any action). We will
re-t
We are overjoyed to announce the release of:
os-api-ref 1.1.0: Sphinx Extensions to support API reference sites in
OpenStack
With source available at:
http://git.openstack.org/cgit/openstack/os-api-ref
For more details, please see below.
Changes in os-api-ref 1.0.0..1.1.0
-
A translation review trickled in late for searchlight-ui. So we cut a RC3:
https://tarballs.openstack.org/searchlight-ui/searchlight-ui-1.0.0.0rc3.tar.gz
Thanks,
Dims
On Thu, Sep 29, 2016 at 11:09 AM, Davanum Srinivas wrote:
> Hello everyone,
>
> The release candidate for searchlight for the en
Hi Lenny Verkhovsky,
Thank you for your response.
I am using the Mitaka version of openstack. I followed the
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking and set
the "intel_iommu=on".
Here is the output for the VF's config
root@A1-22932-compute1:~# cat /proc/cmdline
BOOT_IM
"Testing: call tempest function from tox"
https://blueprints.launchpad.net/openstack-ansible/+spec/testing-direct-tem
pest
I filed this blueprint for a potential enhance to our functional testing.
Any thoughts OSA team?
Michael Gugino
On 9/29/16, 1:38 PM, "Davanum Srinivas" wrote:
>Hello
I’d like to also toss my name into the ring. I’m announcing my candidacy
for a
position on the OpenStack Technical Committee.
-- About me
I have served as the Keystone PTL for the Mitaka and Newton cycles, and will
again serve as the PTL for the Ocata cycle. I’ve also contributed heavily to
python
I am throwing my hat into the ring for the TC election.
I've been a part of OpenStack since it started. I've seen it grow from
a few dozen people into the very large community we have today. During
the past 6 years, I've seen controversial topics come and go and the
community grow and adapt. I've
Michal,
I didn’t say we had to run two parallel implementations at the same time to be
compliant with this project maturity tag. We have to maintain it in the
release for 3 months until we switch to something else if our intent is to
switch to something else (at 3 months + 1 picosecond ☺. Rea
Hello everyone,
A new release candidate for Nova for the end of the Newton cycle
is available! You can find the source code tarball at:
https://tarballs.openstack.org/nova/nova-14.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this candidate wi
Hello everyone,
A new release candidate for Designate for the end of the Newton cycle
is available! You can find the source code tarball at:
https://tarballs.openstack.org/designate/designate-3.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, thi
Hello all,
So for many years we've been using either the service defaults
(usually python determined processor count) or the $processorcount
fact from facter in puppet for worker configuration options for the
OpenStack services. If you are currently using the default values
provided by the puppet
Howdy folks,
I'd like to submit myself as a candidate for the OpenStack TC,
The reasons why are varied (and longer than I can list here) but it
really comes to my desire to see OpenStack succeed and prosper and
exist (in whatever shape and form) going forward in a way that is
sustainable for the
On 29/09/16 04:35 PM, John Dickinson wrote:
>
> I am concerned that there is a current focus on preserving the status
> quo. There's focus on policies and rules instead of use cases; there's
> focus on conformity instead of innovation; there's focus on forced
> prioritization instead of inclusivi
https://review.openstack.org/379850
Let's make OpenStack great again.
If you don't know me, I'm very good. The code and designs I make
are tremendous, and I intend to contribute to the TC bigly. The other
candidates are sad, and they want OpenStack to be a third world project,
no good.
OpenStack
On 09/29/2016 06:14 PM, Clint Byrum wrote:
> https://review.openstack.org/379850
>
> Let's make OpenStack great again.
>
> If you don't know me, I'm very good. The code and designs I make
> are tremendous, and I intend to contribute to the TC bigly. The other
> candidates are sad, and they want O
I am standing as a candidate for a seat on the OpenStack Technical
Committee.
I have worked with OpenStack since the Diablo days and have done it full
time since joining the OpenStack Infrastructure team during the Folsom
cycle. During this time I have been an OpenStack developer, operator,
and us
I guess I'll send a copy of mine to the ML too, since all the cool
kids seem to be doing it...
Most of you probably know me as "that short dude in the Hawaiian
shirt and long hair." I'll answer to "Jeremy," "fungi" or even just
"hey you." I'm starting my third cycle as PTL of the Infrastructure
te
Hi folks,
Yes, I think there are some discrepancies around the provisioning
status being exposed.
Currently I think the only way to get visibility to those is through
the status api:
http://developer.openstack.org/api-ref/networking/v2/#show-load-balancer-status-tree
Which, frankly, I think there
On 29 Sep 2016, at 16:00, gordon chung wrote:
>
> On 29/09/16 04:35 PM, John Dickinson wrote:
>>
>> I am concerned that there is a current focus on preserving the status
>> quo. There's focus on policies and rules instead of use cases; there's
>> focus on conformity instead of innovation; there'
I believe this is the voice we really need in the TC.
THANK YOU.
- Qiming
On Thu, Sep 29, 2016 at 11:47:12PM +, Jeremy Stanley wrote:
> I guess I'll send a copy of mine to the ML too, since all the cool
> kids seem to be doing it...
>
> Most of you probably know me as "that short dude in the
B.R.,
Zhijiang
__
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
1) Roll Call
2) Core Code Abstraction
3) Bifrost/Ironic Integration
4) OPNFV: Daisy4nfv CI Framework Progress
5) Bare Metal Deployment(PXE/IPMI) demo2 doc and artifact
B.R.,
Zhijiang
__
OpenStack Development Mailing List (no
Hi ironic team：
I reported a bug of "get pci device's numa_node info when collecting
pci devices info" on ironic-python-agent launchpad.
this is the bug link:
https://bugs.launchpad.net/ironic-python-agent/+bug/1622940
And here is the commit: https://review.openstack.org/#/c/369245/
Coul
etherpad: https://etherpad.openstack.org/p/Trio2oCleaning
Best Regards
Chaoyi Huang (joehuang)
From: joehuang
Sent: 29 September 2016 10:59
To: openstack-dev
Subject: [openstack-dev][trio2o]Trio2o cleaning discussion
Hello,
As we discussed yesterday, we'll have a
Hey Everyone,
Some of you may know me, I've been around the OpenStack community for a
while (longer than some, shorter than others). I'm not an "uber hipster",
or a "super cool bro-grammer", or even a "mega hacker" trying to write the
most clever code possible to impress everyone.
I am however s
Hello, all
All "must to have" patches have been merged, the "stable/newton" branch was
just created: https://github.com/openstack/tricircle/tree/stable/newton
Before the newton release, two more patches needed for this branch: one patch
to update devstack related script to download newton branc
Hi everyone,
We're on the final countdown to Newton now! The release managers Olena and Alex
are busy getting the release patches ready, the Install Guide testing team are
madly working through the last few sections, and Andreas and I have our fingers
hovering over the big red GO button! Don't
My Peers,
I am self-nominating for serving you as your technical committee
representative.
I won't bore you with my professional accomplishments. If you want to
see such information to judge if I'm qualified for serving you on the
technical committee team, that information is available in my
fou
88 matches
Mail list logo
