hat's makes sense. I'll update the review with that change.
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github}
http://blog.oddbit.com/|
__
OpenStack Development Mailing List (not for u
iew.openstack.org/#/q/topic:feature/firewall%20(status:open%20OR%20status:merged)
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github}
http://blog.oddbit.com/|
__
OpenStack Development Mailing List
ee that points at an
actual idempotency issue?
(I wouldn't be at all surprised to find an actual problem in this
change; I've fixed several already. I'm just not sure how to turn
this failure into actionable information.)
--
Lars Kellogg-Stedman
pet-keystone/blob/master/spec/acceptance/default_domain_spec.rb#L59
I've been staring at this for a while and I'm not sure what's going
on.
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github}
http://blog.oddbit.com/|
_
On Thu, Jun 28, 2018 at 8:04 PM, Lars Kellogg-Stedman
wrote:
> What is required to successfully run the rspec tests?
On the odd chance that it might be useful to someone else, here's the
Docker image I'm using to successfully run the rspec tests for
puppet-keystone:
https
ossibly
conflicting.
This only affects module lib directories. As Alex pointed out, puppet
classes themselves behave differently and don't conflict in this
fashion.
--
Lars Kellogg-Stedman | larsks @ {irc,twitter
exists only to provide a set of
host_prep_tasks:
https://github.com/CCI-MOC/rhosp-director-config/blob/master/templates/services/patch-puppet-modules.yaml
Is there a better way to do this?
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,githu
rake aborted!
can't modify frozen Symbol
What is required to successfully run the rspec tests?
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github}
http://blog.oddbit.com/|
__
OpenStack Development
stack overcloud deploy` command. Is
there a way to refer to "the current templates directory"?
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github}
http://blog.oddbit.com/|
__
OpenStack Developme
I've noticed that when updating the overcloud with 'overcloud deploy',
the deploy process does not restart the haproxy containers when there
are changes to the haproxy configuration.
Is this expected behavior?
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github}
http://
playbooks or something.
On the other hand, I like your suggestion of just ditching
DeployArtifacts for a new composable service that defines
host_prep_tasks (or re-implenting DeployArtifacts as a composable
service), so I'm going to look at that as a possible alternative to
what I
On Mon, Jun 18, 2018 at 11:31:08AM -0400, Mohammed Naser wrote:
> Hey Lars,
>
> Do you have a full job that's running which shows those issues?
I don't. I have a local environment where I'm doing my testing.
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github
e *none* of
the puppet types or providers have a "new" method as far as I can see.
Any pointers you can offer would be appreciated.
Thanks!
--
Lars Kellogg-Stedman | larsks @ {irc,twitter,github}
http://blog.oddbit.com/|
___
d then use upload-swift-artifacts:
upload-swift-artifacts -f patches/puppet-modules.tar.gz
Done this way, I get the output I expect.
[1]:
https://github.com/openstack/tripleo-heat-templates/blob/master/docker/docker-puppet.py
On Wed, Sep 13, 2017 at 7:45 PM, Michał Jastrzębski
wrote:
> We would to ask for volunteer project team to join us and spearhead this
> effort.
>
>
I would certainly be interested in this effort.
--
Lars Kel
that jbadiapa is doing for
containerized fluentd in Pike. I'd like to make sure that Pike has settled
before landing these.
--
Lars Kellogg-Stedman
__
OpenStack Development Mailing List (not for usage questions)
U
ure and there's a good
chance that it's already running, particularly in tripleo target
environments).
--
Lars Kellogg-Stedman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
t the same message rate
limiting we get with fluentd.
Based on the above, I would like to suggest exploring a syslog-based
logging model moving forward. What do people think about this idea? I've
started putting together a spec at https://review.openstack.org/#/c/484922/
and I would welcom
ut!
[1] Initially, Dan Prince, Ian Main, Martin Mágr, Lars Kellogg-Stedman
--
Lars Kellogg-Stedman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
-- seems like an excellent goal. Using Heat as a
"front-end" to the process means that we get to keep the parameter
validation and documentation that is missing in Ansible, while still
following the Unix philosophy of giving you enough rop
While investigating a bug report against cloud-init ("why don't you put
nameservers in interface configuration files?"). I discovered that Nova
munges the information received from Neutron to take the network-scoped
nameserver entries and move them all into a global "services" section.
It turns ou
oot_group explicitly
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP signature
__
OpenStack Development Mailing
be sufficient such
that it will use images generated with the dependent patch?
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description:
I would like to request a feature freeze exception for the collectd
composable service patch:
https://blueprints.launchpad.net/tripleo/+spec/tripleo-opstools-performance-monitoring
The gerrit review implementing this is:
https://review.openstack.org/#/c/411048/
The work on the composable s
rewall rules implementation helped me
understand how the service_config_settings stuff works.
You can see the updated implementation at:
- https://review.openstack.org/#/c/417509/ (puppet-tripleo)
- https://review.openstack.org/#/c/411048/ (t-h-t)
--
Lars Kellogg-Stedman | larsks @ {freenode,twitt
t; resource, which only exists as a way to expose
certain parameter_defaults inside services.yaml.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP signature
___
s.
I'd appreciate your feedback on this idea. Thanks!
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP signature
names defined in the 'parameters' section. It's not really
very pretty, but it has at least prevented me from committing some
changes with egregious spelling errors.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | ht
t;master tripleo" user is not able to modify the
environment of my "rdo release" user).
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP signature
_
- in puppet-tripleo: https://review.openstack.org/#/c/353507
I am looking for someone on the tripleo team to take a quick look at how
this is laid out and give a thumbs-up or thumbs-down on the current
design.
Thanks,
* There is also a corresponding spec which should be posted soon.
--
Lars Ke
roles that are typically
installed together?
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP signature
__
OpenSta
2 from me. Gabriel has done some good work and he has put up with
my reviews :).
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP
(and then retry the connection
in the background)?
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP signature
__
rom where
things are now.
I leave the decision about where things are going to someone who has a
more vested interest in the resolution.
Cheers,
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Descri
,
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
pgp4e0rmRGFeO.pgp
Description: PGP signature
__
OpenStack Development Mailing List (not for usage
for RHEL7.1/Centos7.
Fedora and CentOS (7) both have libyaml and libyaml-devel. I wonder
if this is just a package naming issue in devstack? libyaml-devel is
used by PyYAML to build C extensions, although PyYAML will also
operate without it.
--
Lars Kellogg-Stedman | larsks @ {freenode,t
tended. Note that CoreOS does *not*
use the same cloud-init that everyone else uses, and it is entirely
possible that the CoreOS cloud-init does not support multipart MIME
user-data.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http
t; branch.
The previous version of the templates, which worked with F20 and
included some Kolla-specific networking logic, is available in the
"kolla" branch:
https://github.com/larsks/heat-kubernetes/tree/kolla
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Clou
gt; comments, as well as implementing neutron and helping get nova-networking
> implementation rolling.
>
> Please vote +1 or -1 if your kolla core. Recall a -1 is a veto. It takes 3
> votes. This email counts as one vote ;)
+1
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,g
ny day now") will sport a
shiny new "docker exec" command that will provide you with the ability
to run commands inside the container via the docker client without
having to involve nsenter (or nsinit).
It looks like:
docker exec ps -fe
Or:
docker exec -it bash
--
ise, I think establishing a "best practice" mechanism for executing
in-container checks is a great idea.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
pgpD1P2Vb3KMF.pgp
Description: PGP signature
uldn't spend time worrying about that. "docker exec" will be the
standard way as soon as it lands in a release version, which I think
will be happening imminently with 1.3.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack
in and support those applications.
I think it's entirely accurate to say that they are
application-centric, much like services such as Heroku, OpenShift,
etc.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
pg
but is actually "write an application
that uses a database backend".
I think there are uses cases for both "official" and customized
images.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
pgpKaSD
e discovery
mechanism; there are many available (etcd, consul, serf, etc).
But this isn't particularly a docker problem. This is the same
problem you would face running the same software on top of a cloud
environment in which you cannot predict things like ip addresses a
priori.
--
Lars Kell
#x27;t "yum upgrade" or "apt-get upgrade"
in a container; you generate a new image with new packages/code/etc.
This makes it trivial to revert to a previous version of a deployment,
and clearly separates the "build the image" process from the "run the
applic
riadb-1
version: v1beta1
id: mariadb
labels:
name: mariadb
With this configuration, you could kill the mariadb container, have it
created on other minion, and you would still have access to all the
data.
This is meant simply as a way to experiment with storage and
kubernetes.
--
Lars Ke
container, because that generally makes the
question of process supervision and log collection a *host* problem
rather than a *container* problem. It also makes it easier to scale an
individual service, if that becomes necessary.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engi
kubernetes/issues/1161 and try to
> follow the "standard" kubernetes approaches as they emerge.
Yup, I think that is definitely the way to go.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
pgpJN
rectly.
You cannot kill either the glance or mariadb pods because we do not
yet have a solution for persistent storage.
I will be cleaning up these changes and submitting them for review...but
probably not today due to an all-day meeting.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,gi
out/stderr and not to local files.
If you know your container's ENTRYPOINT and CMD entries, you can run
those by hand to see exactly what is happening.
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack
try
to re-create the stack.
Do folks have an opinion on which behavior is correct?
--
Lars Kellogg-Stedman | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
pgp0HRMLHzOb7.pgp
Description: PGP
is restores access to the metadata service. This forces the
kernel to pass traffic to 169.254.169.254 to the gateway, rather than
assuming it's accessible via a local network.
--
Lars Kellogg-Stedman | larsks @ irc
Cloud Engineering / OpenStack | " " @ twitter
pgpj
On Thu, Jan 30, 2014 at 09:46:09PM -0500, Lars Kellogg-Stedman wrote:
> I'm getting an error from Keystone whenever I try to signal a Heat
> WaitCondition...
After poking through the code it turned to be an error in Keystone's
contrib/ec2/controllers.py...which was fixed in 9
ed4ea1886ead9f98451f5a&SignatureVersion=2&Signature=9c2bvEYoedkm3uQwVOAcIA5xxy3x9q%2BO1KncY8Eeo%2BQ%3D
I've tried signaling this both using cfn-signal and using the
generated curl commandline directly. I'm using a recent (sometime
this past week) Heat master, and Keys
mplete
your initial configuration:
ip route add blackhole 169.254.169.254
This prevents access to the metadata unless someone already has root
access on the instance.
--
Lars Kellogg-Stedman | larsks @ irc
Cloud Engineering / OpenStack | " " @ twitter
pgp4mFXCAneZr
nd above, but I want to see DEBUG messages for
quantum.plugins.openvswitch.agent.ovs_quantum_agent.
Or is that Too Much Flexibility?
--
Lars Kellogg-Stedman
pgp4FTOI0Dp6d.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-d
Kellogg-Stedman
pgpEhsBnmW49t.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
58 matches
Mail list logo
