root-wrap failed probably a config error. might want to post your nova
configs with commenting out of passwords / service tokens.
dnsmasq --strict-order --bind-interfaces --conf-file=
--pid-file=/var/lib/nova/networks/nova-br100.pid
--listen-address=192.168.22.1 --except-interface=lo
--dhcp-range
on the below?
>>>
>>> Thanks,
>>> Dev
>>>
>>> On Fri, Jul 10, 2015 at 4:32 PM, pra devOPS
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> I am running as root, Please find below the nova config file. ( I am
>>>
yeah that really didn't belong in glance at all.
On Tue, Jul 28, 2015 at 10:05 AM, Flavio Percoco wrote:
> On 27/07/15 19:24 +, Ian Cordasco wrote:
>
>>
>>
>> On 7/27/15, 11:29, "Louis Taylor" wrote:
>>
>> On Fri, Jul 17, 2015 at 07:50:55PM +0100, Louis Taylor wrote:
>>>
Hi operators,
Caius why not submit that patch to openstack review for cinder? I'm sure
more than a few of us would be glad to voice our desire for it or something
much like it to land in liberty.
-Matt
On Wed, Jul 29, 2015 at 10:36 AM, Caius Howcroft
wrote:
> Hi,
>
> We (bloomberg) are pre
it was worth noting.
Thanks for asking and being awesome as always! You rock!
-matt
On Wed, Aug 5, 2015 at 10:50 AM, Adam Young wrote:
> How do you delegate the ability to delegate?
>
> Lets say you are running a large cloud (purely hypothetical here) and you
> want to let a user man
Under no environment would I attempt this. You would need at the very
least satellite controllers.
On Wed, Oct 14, 2015 at 6:38 PM, piotr.mis...@prokonto.pl <
piotr.mis...@prokonto.pl> wrote:
> Hi,
>
> Do you know if there is a possibility to manage tenants networks in many
> OpenStack environme
backporting patches isn't too terribly hard to be honest. you could
probably hire a consultant to do it if need be. mirantis would probably
quote you a price.
On Fri, Nov 6, 2015 at 3:10 PM, Fox, Kevin M wrote:
> Kind of related, as an op, we see a lot of 3rd party repositories that
> recently
tons from what i've seen. there are a LOT of havana and even earlier stuff
out there. essex is still out there in the wild.
On Mon, Nov 9, 2015 at 2:18 PM, Jeremy Stanley wrote:
> On 2015-11-09 19:01:36 + (+), Tom Cameron wrote:
> [...]
> > What do the user/operator surveys say about t
Hell. There's no clear upgrade path, and no guaranteed matched
functionality just for starters.
Also most enterprise deployments do 3 to 5 year deployment plans. This
ties into how equipment / power / resources are budgeted in the project
plans. They don't work with this mentality of rapid rel
=D
On Mon, Nov 9, 2015 at 3:43 PM, Tom Cameron
wrote:
> YOLO. Because it's in The Cloud.
>
>
>
> --
> Tom Cameron
>
>
>
> --
> *From:* Donald Talton
> *Sent:* Monday, November 9, 2015 15:41
> *To:* matt; Tom Cameron
>
kilo. They end up either having to do a double rolling upgrade or just
migrate vms into a new environment and repattern their former compute nodes
as new members of the cluster.
Just a few of the many hurdles I can think of off the top of my head.
Matt
On Mon, Nov 9, 2015 at 4:05 PM, Sean Dagu
deployers.
-Matt
On Mon, Nov 9, 2015 at 4:25 PM, matt wrote:
> Sean,
>
> I am not sure this can be completely or even satisfactorily addressed
> by the OpenStack community. A part of the problem is supporting
> environment. As OpenStack advances it relies on advancing under
i'd recommend using jenkins or some sort of packaging utility whatever or
just python setuptools to create a venv of each of the components before
using puppet to deploy them.
-matt
On Fri, Nov 13, 2015 at 2:07 AM, Okan bhan wrote:
> Hi Guys,
>
> I'm trying installing Ope
Yeah, I'd like to see that as well. Joe Tapajian would be my pick. But I
don't see that happening. Operators just don't have the voting power the
devs do. Unless someone wants to spam their own corp backers for voting
support ( not really ethical, though obviously being done ).
community is large enough for such a representation.
>
> Can you elaborate on operators lacking the power?
>
>
> On Nov 23, 2015, at 11:39 AM, matt wrote:
>
> Yeah, I'd like to see that as well. Joe Tapajian would be my pick. But I
> don't see that happening.
Worth trying for sure.
On Tue, Nov 24, 2015 at 6:06 AM, Thierry Carrez
wrote:
> matt wrote:
> > it's a voted position. there just aren't that many operators who vote
> > compared to devs and other contributors. to say nothing of
> > non-contributors who sign up
rd:
https://www.openstack.org/community/jobs/
You can post for free
-Matt
On Tue, Nov 24, 2015 at 3:07 PM, Adam Lawson wrote:
> For the consultants reading this (I've pretty much exhausted my Rolodex):
> I have a remote engineering opportunity if someone wants a little side work
> thi
my guess is horizon admin panels would bomb out... but it would be trivial
to replace the admin panels with a warning page.
-matt
On Tue, Oct 21, 2014 at 10:23 AM, Adam Young wrote:
> On 10/20/2014 12:11 AM, Tim Goddard wrote:
>
>> Hello all,
>>
>> We have an establishe
My fear with the github is that people will just donate code in a fire and
forget fashion... this will generate a poorly maintained repo in which
finding useful actively maintained contributions may become difficult.
So my concerns lie in ensuring that anyone who contributes to this effort
is comm
hing like cloud foundry. I don't know what the solution is.
Maybe for now there is not one.
-Matt
On Mon, Nov 10, 2014 at 2:52 PM, Tim Bell wrote:
> So, how about maintaining a set of pointers to the github repos where we
> are all working ?
>
>
>
> We publish and mai
with monitoring my experience is that scale really matters. what is your
footprint in some sort of quantified range of number of physical hosts vs
vms?
On Mon, Nov 10, 2014 at 4:23 PM, Kris G. Lindgren
wrote:
> Hello Operators,
>
> Was wondering what you are using to gather Openstack telemet
the only issue with nova-network here is that it's FINALLY slated to be
removed in the next release.
so yes it will work, and it may even be optimal for this size deployment,
but it will NOT be at all future proofed.
I'd go with neutron as of now.
-matt
On Sat, Dec 20, 2014 at 5:16
missed that last question.
yes i've put management services on compute nodes in mild production. It
works fine.
-matt
On Sat, Dec 20, 2014 at 6:09 PM, matt wrote:
> the only issue with nova-network here is that it's FINALLY slated to be
> removed in the next release.
>
&g
Sounds like a solid way to approach it george. I hope you can document and
share your methods and experiences.
Sounds like this would be helpful to folks setting up small test
environments.
On Mon, Dec 22, 2014 at 4:35 PM, George Shuklin
wrote:
> Thank you for everyone!
>
> After some lurking
There are several fundamental problems in getting your feet wet in
OpenStack.
First is that OpenStack is expecting to be installed into a rack of
systems, not one system. While there are work arounds such as devstack,
they fail to accurately produce a production environment or even a useful
facsi
we're all entitled to our opinions =P
I wouldn't classify ubuntu cloud archive as a distro.
On Tue, Dec 30, 2014 at 10:52 AM, Jay Pipes wrote:
> On 12/30/2014 10:40 AM, matt wrote:
>
>> I think there was a view early on that distributions of openstack would
>> em
It might be good to setup some sort of collaborative set of reference
architectures for some basic examples of OpenStack in different areas.
On Tue, Dec 30, 2014 at 4:18 PM, James Dempsey
wrote:
> On 31/12/14 05:09, Stuart Fox wrote:
> > Hi James
> >
> > Great question and some good answers so f
edly see some big changes on this front. Hopefully they are driving
towards the ease of deployment for new users. That would be a wonderful
thing. Be that as it may, there are some considerable hurdles to that.
-Matt
On Thu, Jan 1, 2015 at 8:23 PM, Adam Lawson wrote:
> That sounded a bi
Might be better to send this one the direction of the OSSG list. I know
some of the HP guys over there like rob clark and jamie finnegan might.
On Tue, Jan 6, 2015 at 5:49 AM, Tim Bell wrote:
>
>
> Does anyone have experience of open source host and network intrusion
> detection with OpenStack
Also there are tap aggregations solutions out there for shunting traffic
flows into IDS / etc. That's more of an outside openstack thing right now
though.
-matt
On Tue, Jan 6, 2015 at 12:38 PM, matt wrote:
> Might be better to send this one the direction of the OSSG list. I know
&
Hey Mike!
Thanks for this info. Super helpful to me at least. I am very interested
in hearing more about nova-network to neutron migrations.
-Matt
On Tue, Jan 13, 2015 at 1:53 PM, Michael Still wrote:
> Hi, I just wanted to make sure people know that a small group of us
> got togethe
o augment
ceilometer.
-Matt
On Thu, Jan 15, 2015 at 9:25 AM, Mathieu Gagné wrote:
> On 2015-01-15 11:43 AM, Jesse Keating wrote:
>
>> We have a need to better manage the various openstack capacities across
>> our numerous clouds. We want to be able to detect when capacity of o
Will do.
On Thu, Jan 15, 2015 at 12:08 PM, Anita Kuno wrote:
> On 01/14/2015 01:06 PM, matt wrote:
> > Hey Mike!
> >
> > Thanks for this info. Super helpful to me at least. I am very
> interested
> > in hearing more about nova-network to neutron migrations.
from
our nagios plugin that did dynamic disk free analytics. I don't have any
of the animated GIFs I made that showed fluctuations over days... but that
was great from a human visual sense.
I suppose this could be further automated and refined, I've not been
focused here anymore though.
+1
On Sun, Jan 18, 2015 at 10:05 PM, Jay Pipes wrote:
> On 01/15/2015 05:20 PM, George Shuklin wrote:
>
>> Hello everyone.
>>
>> One more thing in the light of small openstack.
>>
>> I really dislike tripple network load caused by current glance snapshot
>> operations. When compute do snapshot,
least management types did not like that they couldn't really edit our
documentation.
-matt
On Mon, Jan 26, 2015 at 5:10 AM, George Shuklin
wrote:
> We using chef to manage hosts. Data bags contains all data of all hosts.
> We keep hardware configuration and DC-wide-name in d
are perfect place for
> updates and ideas for future update.
>
> Yes, it is a mess, but it is better than 'not enough information because
> of the format restrictions'.
>
>
>
> On 01/26/2015 03:45 PM, matt wrote:
>
> I really liked using sphinx for document
python-openstackclient had a csv output last i checked.
On Wed, Jan 28, 2015 at 6:40 AM, Jesse Pretorius
wrote:
> On 28 January 2015 at 06:19, Tim Bell wrote:
>
>> +1 for commas. Configuration files with JSON is OK but commas for CLIs.
>>
>
> +1 for commas from an operator perspective
>
>
kinda tempted to suggest using some sort of like NSA project code name
generator. Keeps it short, memorable, and unique.
Example Possible Image Names:
Lackluster Aardvark
Screaming Potato
Languid Porpoise
On Thu, Feb 5, 2015 at 10:45 AM, George Shuklin
wrote:
> Updated report for 'no image'
It's certainly a pain to diagnose.
On Thu, Feb 5, 2015 at 3:19 PM, Kris G. Lindgren
wrote:
> Is Mirantis going to have someone at the ops mid-cycle? We were talking
> about this in the operators channel today and it seemed like pretty much
> everyone who was active has problems with rabbitmq.
something but the ram
limitations do suck there.
Was curious if anyone had any preferences on this front.
-Matt
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
gt;
> Great little machines, make sure you update the firmware!
>
> We did a talk on the setup 2 summits ago, and we’re looking to provide
> an update on using them at Vancouver
>
> --Will Snow
> was...@cisco.com
> Director, OpenStack Customer Engineering
> Mobile: +
3) no 10 gig.
On Wed, Feb 11, 2015 at 11:29 AM, matt wrote:
> i dislike 2 things about the NUCs...
>
> 1) only a single interface
> 2) no lights out management
>
> =/
>
> On Wed, Feb 11, 2015 at 11:06 AM, Will Snow (wasnow)
> wrote:
>
>> Yes, I was cons
i dislike 2 things about the NUCs...
1) only a single interface
2) no lights out management
=/
On Wed, Feb 11, 2015 at 11:06 AM, Will Snow (wasnow)
wrote:
> Yes, I was considering waiting for the new NUCs but they’re March
> (scheduled) which means general availability sometime after that.
>
the lack of lom is... difficult in this use case. more so than any of the
other 3 defficiencies i listed.
I wonder if an after market lom board exists.
On Wed, Feb 11, 2015 at 12:19 PM, Jesse Keating wrote:
> On 2/11/15 9:12 AM, Will Snow (wasnow) wrote:
>
>> I do miss LOM on the boxes tho – t
i mean for on and off i can just install a networked mcu. that's easy.
On Wed, Feb 11, 2015 at 1:42 PM, Christian Berendt
wrote:
> On 02/11/2015 05:29 PM, matt wrote:
> > 2) no lights out management
>
> If you only have to turn on/off the NUCs have a look at reBot pro
o you reset bios
configs remotely? how do you get serial console?
that's tricky.
-matt
On Wed, Feb 11, 2015 at 1:42 PM, Christian Berendt
wrote:
> On 02/11/2015 05:29 PM, matt wrote:
> > 2) no lights out management
>
> If you only have to turn on/off the NUCs have a lo
http://www.intel.com/content/www/us/en/nuc/nuc-kit-dc53427hye.html has
intel AMT apparently. this is an intel only lom like thing.
On Wed, Feb 11, 2015 at 1:55 PM, matt wrote:
> for the record rebot is a terrible solution. Any mcu's gpio should be
> able to take over for the on /
yeah i found that and was reading... i mean it sucks it's not ipmi
compatible... but at least it's something.
would NEVER use in prod without interface isolation. but for a demo
rig it kinda works.
still wish the nuc had a second interface... even more so now.
-matt
On Wed, Fe
r own LOM board.
Then all you need to do is re-implement IPMI protocol and tie it to the
hardware.
Half way to an open source LOM board at that point.
But honestly, with AMT that's not really necessary here.
Still... open source LOM would be nice.
-matt
On Wed, Feb 11, 2015 at 3:19 PM, Abel
Jesse the AMT looks like it may work in so far as functionality... but it
requires unix utility amttool in place of ipmitool.
I'll report back on how these work for me.. I just ordered 4 for testing.
Only that one model of the NUCs has AMT support with vpro on it. So if you
do go nuc
http:/
for billing though.
>
>
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy, LLC.
>
>
>
> On 2/12/15, 9:17 AM, "Matt Joyce" wrote:
>
> >I thought stacktach was more in the vein of diagnostic. Not billable
> >resou
I am working on a 1u mount system right now for some demo rig stuff at
work... I'm looking to inline 4 NUCs to start. I'll document when I am
done.
-matt
On Mon, Feb 16, 2015 at 5:33 PM, Sriram Subramanian
wrote:
> Why do you think this is silly? When you say 'different syst
I like cowbuilder... pbuilder using copy on write qcow's for the build
environment. Most folks automating debian package creation use pbuilder.
-Matt
On Wed, Mar 4, 2015 at 11:31 AM, Mathieu Gagné wrote:
> Hi,
>
> I'm currently experimenting with fpm.
>
> I learned t
use a pgp signing key with pass phrase and sign the release / packages
files. ubuntu already does this.
On Wed, Mar 4, 2015 at 12:39 PM, Mathieu Gagné wrote:
> On 2015-03-04 12:18 PM, Clint Byrum wrote:
>
>> Excerpts from Mathieu Gagné's message of 2015-03-04 08:31:45 -0800:
>>
>>>
>>> I really
and thus different keys.
so what's the issue?
On Wed, Mar 4, 2015 at 1:16 PM, Mathieu Gagné wrote:
> On 2015-03-04 1:10 PM, matt wrote:
>
>> use a pgp signing key with pass phrase and sign the release / packages
>> files. ubuntu already does this.
>>
>>
&
irect to me. I'll get a list of volunteers
going. We can go from there. Or someone else can totally run this instead
of me if they feel they can do a better job ( they probably can =P ).
-Matt
___
OpenStack-operators mailing list
OpenStack
that timeout is probably in the HTTP server. it also depends how it's
executing in the http server. django
-matt
On Thu, Mar 12, 2015 at 4:57 PM, Muthulakshmi S wrote:
> Thanks, nova secgroup-list took 0m30.250s to list two sec grps in Admin
> tenant,
>
> quantum securit
packaging / deployment guide extends from this etherpad discussion:
https://etherpad.openstack.org/p/PHL-ops-packaging
-matt
On Thu, Mar 12, 2015 at 3:37 AM, Andreas Jaeger wrote:
> On 03/11/2015 04:09 PM, matt wrote:
> > One take away from the OpenStack operators meetup in philly
lack of
knowledge about how to work with it in a packaging scenario.
-Matt
On Fri, Mar 13, 2015 at 4:56 PM, Subbu Allamaraju wrote:
> Regarding the discussion on tags, here is my take from the discussion on
> Monday.
>
> 1. There is vehement agreement that having an integrated releas
most openstack environments at kvm, so if you want to stick with the herd,
that's the way to go.
On Wed, Mar 18, 2015 at 5:53 PM, Abel Lopez wrote:
> Interesting topic, since you're already running Hyper-v and ESX, I'm
> inferring that your workload is heavy on windows VMs.
> If you're doing maj
the size of your cluster, you may have other factors to
> consider such as monitoring and configuration management. We use Puppet to
> configure both environnments.
>
>
>
> Images are tagged with a property hypervisor_type which is used to
> schedule workloads to the appropriate hyp
paying more for windows licenses then if you did kvm for the free os's.
>
> Thanks,
> Kevin
>
> --
> *From:* matt [m...@nycresistor.com]
> *Sent:* Thursday, March 19, 2015 9:36 AM
> *To:* Fox, Kevin M
> *Cc:* maishsk+openst...@maishsk.com;
we should get a thank you cake to put in the dev summit area with a ref to
the review number on it =P
On Tue, Mar 24, 2015 at 2:25 PM, David Medberry
wrote:
> and also that Mehdi's oslo.messaging heartbeat fix for rabbitmq has merged
> and there is intent to get that client version into Kilo. (A
Not sure I'd call devstack configuration management.
On Thu, Mar 26, 2015 at 3:13 PM, John Dewey wrote:
> We are also in the process of looking at stackstorm[1] as a means to
> operate openstack. The ability limit playbook execution based on a users
> role, perform auditing, and automatic reme
referring to Tim Bell's link =P
On Thu, Mar 26, 2015 at 3:45 PM, Matthew Kaufman wrote:
> hey Matt, nice seeing you last night - who said anything about devstack
> here?
>
> On Thu, Mar 26, 2015 at 3:30 PM, matt wrote:
>
>> Not sure I'd call devstack configuratio
t all the shell script craziness in
> devstack with ansible. Devstack becomes the reference architecture to
> deploying openstack. Deploying to a workstation, or multi-node, or
> production is a matter of swapping out the site.yml.
>
> On Thursday, March 26, 2015 at 12:51 PM, ma
Man I'd love for some mesos integration with openstack...
On Thu, Apr 23, 2015 at 3:31 PM, Fox, Kevin M wrote:
> I'm thinking more like this use case:
> I'm a cloud user, I want a new Trac site. or an Elastic Search cluster. Or
> a Jenkins system for my project. Why do I have to take a lot of ti
; Andrea
> May 6 2015 3:31 PM, "Matt Van Winkle" wrote:
> > Was there discussion about this at the mid-cycle? I'd love to see if
> > there is any background info for context besides the entries in [1]. Is
> > the desire to trade best practices or start pushing fo
The fundamental problem with a CMDB implementation as I see it, is you are
effectively in need of a shared comm services for fast action small meta
data sets.
That becomes a project all in it's own right.
-matt
On Wed, May 6, 2015 at 10:36 PM, Allamaraju, Subbu wrote:
> Hi Tom,
>
&
honestly that seems like a very useful feature to ask for... specifically
for upgrading qemu.
-matt
On Wed, May 13, 2015 at 11:19 AM, Daniel P. Berrange
wrote:
> On Wed, May 13, 2015 at 03:08:47PM +0000, Matt Van Winkle wrote:
> > So far, your assessment is spot on from what we&#x
A worthwhile discussion. But are we talking about this as it relates to
packaging or as a separate track related to the architectural and
procedural challenges?
-matt
On Thu, May 14, 2015 at 12:06 PM, Matt Kassawara
wrote:
> I propose that we spend more time discussing how to improve
that makes more sense to me.
On Thu, May 14, 2015 at 12:13 PM, Matt Kassawara
wrote:
> Wouldn't this replace the database session... not the packaging session?
>
> On Thu, May 14, 2015 at 11:10 AM, matt wrote:
>
>> A worthwhile discussion. But are we talking abou
This seems like a terrible use case, and a terrible idea for openstack and
operators both.
=/
-Matt
On Mon, Jun 15, 2015 at 7:46 PM, Barrett, Carol L wrote:
> Operators – The Enterprise Work Group (formerly known as Win The
> Enterprise) has a team working on a Proof Of Concept for
rhood and they don't need
to hassle their budgeting managers too much for travel approval /
expenses. This is more accessible currently than the summits for many
operators. Let's keep it that way.
-matt
On Tue, Jun 30, 2015 at 11:56 AM, Joe Topjian wrote:
> Hi Tom,
>
>
Mario,
If I remember right I had a similar issue with getting image_props when I
was doing this to pull in custom properties. Through some trial and error
and poking around with pdb I ended up with this:
image_props = spec_obj.get('request_spec', {}).\
get('image', {}).get('pr
There is a known issue where some providers fail when you have an openrc
sourced. I remember it being glance that failed. Bug #1524599
On Nov 11, 2016 4:15 AM, "Justin Cattle" wrote:
> There was two problems here!
>
> The puppet libs in use were coming from the wrong environment - so a
> pretty
ocess
--
Thanks,
Matt Riedemann
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
k.org/pipermail/openstack-dev/2016-July/098703.html
[3]
https://github.com/openstack/nova/blob/b761ea47b97c6df09e21755f7fbaaa2061290fbb/nova/api/metadata/base.py#L179-L187
--
Thanks,
Matt Riedemann
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
On 11/12/2016 8:19 AM, Amrith Kumar wrote:
I'm adding [trove] to the subject as we're interested in where this ends up.
Matt, it may make sense to include other projects that use service VM's if they
are using file injection/configDrive/...
-amrith
Amrith, is that list of p
. One
difference is that I'm not using the metadefs stuff but I don't know if
that is relevant or not.
On Fri, Nov 11, 2016 at 3:24 AM, Keller, Mario
wrote:
> Hello Matt,
>
> I found you blog post to this and tried your code, but the problem is,
> that I get an error:
>
>
On 11/12/2016 8:31 PM, Matt Fischer wrote:
Its pretty hard for me to parse the above or help more without a live
pdb shell looking at this but I wonder if this is a Liberty vs Mitaka
difference? We're still on nova liberty. The nova team may know more
and/or I can figure out more once we up
On 11/13/2016 8:28 AM, Matt Riedemann wrote:
On 11/12/2016 8:31 PM, Matt Fischer wrote:
Its pretty hard for me to parse the above or help more without a live
pdb shell looking at this but I wonder if this is a Liberty vs Mitaka
difference? We're still on nova liberty. The nova team may
On 11/13/2016 9:20 AM, Amrith Kumar wrote:
Matt,
In Barcelona, there was a discussion amongst all projects that used service
VM's. I'm not able to find the actual meeting on my calendar now but here's
the list that I know of so far; I've tagged those projects in the subj
! http://doodle.com/poll/e7fcfhsf4s8cupyi
Matt
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
ential working group,
then that would clearly be the best outcome, although that may be
optimistic ! As has become clear at recent Ops events, it may be that not
all of those companies are represented on these lists, so I'd welcome any
input on the best way to reach
itelist of support handlers.
I also know that lots of deployments probably aren't at Newton yet so
they haven't seen the release notes about the image_file_url config
options being deprecated so I wanted this to be a further heads up
before we go and remove this code.
--
Tha
On 11/14/2016 4:16 AM, Daniel P. Berrange wrote:
On Fri, Nov 11, 2016 at 07:11:51PM -0600, Matt Riedemann wrote:
Chris Friesen reported a bug [1] where injected files on a server aren't in
the guest after it's evacuated to another compute host. This is because the
injected fi
As a part of our upgrades to Newton we are transitioning our services to
use pymysql rather than the deprecated MySQL-Python [1]. I believe pymsql
has been the default in devstack and the gate for sometime now and that
MySQL-Python is essentially untested and not updated, hence our desire to
switch
tp://doodle.com/poll/be43ysxhg5iq3uha
On Tue, Nov 15, 2016 at 10:43 AM, matt Jarvis
wrote:
> So after input from a variety of sources over the last few weeks, I'd very
> much like to try and put together a public cloud working group, with the
> very high level goal of representing
ises questions about standards around naming of objects, network creation
patterns and a bunch of other stuff which I think this WG can start to
address.
Matt
On Tue, Nov 22, 2016 at 7:50 PM, Stefano Maffulli
wrote:
> Hello folks,
>
> On 11/15/2016 02:43 AM, matt Jarvis wrote:
> > I&#
put so far
!
On Mon, Nov 21, 2016 at 8:55 AM, matt Jarvis wrote:
> Whoops, just realised I can't send to these lists with multiple additional
> recipients, so sending again separately ..
>
> Thank you for all of your interest in this proposal. In order to move
> things to the n
heir should be a declared time limit and date
> for achieving a public declaration (and close of the WG). See 'Boston Open
> Science Cloud Congress and forthcoming Declaration' efforts.
>
> [2]= As per all my public correspondence, this is me responding in my
> capacity a
up.
Look forward to seeing you there !
Matt
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
sum of their
> (datacentre) parts, and
> 3.) help jointly advertise and make the wider OpenStack *choice* of the
> marketplace known to the world world.
>
> Looking forward to hearing other ideas and building on the above for 2017.
>
> Kind Regards,
>
> David F. Flanders
+1 from me for 1500 UTC, or other time later or earlier :)
On Tue, Dec 6, 2016 at 3:07 PM, Chris Morgan wrote:
> Today's meeting was held at 14:00 UTC, minutes here
> http://eavesdrop.openstack.org/meetings/ops_meetups_team/201
> 6/ops_meetups_team.2016-12-06-14.25.html
>
> Actually though the m
Awesome work - well done Edgar and team !
On Tue, Dec 6, 2016 at 4:26 PM, Edgar Magana
wrote:
> Team,
>
>
>
> I am gladly informing you that the BoD has just approved our proposal to
> change the OpenStack Bylaws:
>
> https://docs.google.com/document/d/1QmLOeseAkjBWM_
> TXsUeKBErNaSHnuZp81II0T71
uency,
meeting practices and chairs, and to start discussing goals.
Matt
[1] *https://etherpad.openstack.org/p/publiccloud-wg
<https://etherpad.openstack.org/p/publiccloud-wg>*
___
OpenStack-operators mailing list
OpenStack-operators@lists.opensta
eting. IRC logs are in the usual places
http://eavesdrop.openstack.org/meetings/public_cloud_wg/
Thank you to everyone who attended and look forward to exploring this more
next meeting.
Matt
On Wed, Dec 7, 2016 at 10:36 PM, David F Flanders
wrote:
> TL;DR = Let's find one simple task th
is is the specific change mentioned above:
https://review.openstack.org/#/c/205282/
--
Thanks,
Matt Riedemann
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
1 - 100 of 770 matches
Mail list logo
