Hello,
This issue has been active since mid 2014 and still hasn't got any
resolution or fixes merged.
I'm pushing for a fix to this issue and anybody with help or feedback is
welcome.
Please see my last comment on
https://bugs.launchpad.net/nova/+bug/1469179 regarding the old review
which could
Hello,
(I didn't have any luck with this question on the openstack-operators
list so I'm throwing it out here to see if I can catch anyone, according
to Assaf he knew a couple of you devs running a similar environment, if
not feel free to do what you please with this email hehe)
I'm gonna give
Even though I dont have a vote I would like to extend a lot of gratitude
to Mykyta Karpin for
always helping out!
Congratulations and well deserved!
On 01/19/2017 11:28 PM, Alex Schultz wrote:
> Hey Puppet Cores,
>
> I would like to nominate Mykyta Karpin as a Core reviewer for the
> Puppet
On 02/15/2017 01:46 PM, Thomas Goirand wrote:
> Hi there,
>
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
>
> As for many other folks, Mirantis decided to end its
that.
Back to the logs!
Best regards
Tobias
On 11/14/2017 08:35 AM, Tobias Urdin wrote:
Hello,
Same here, I will continue looking at this aswell.
Would be great if we could get some input from a neutron dev with good insight
into the project.
Can we backtrace the timed out message from where
are a lot of users out there using
it! I'd be more than happy to provide any assistance/information in
troubleshooting this.
Thank you,
Mohammed
On Thu, Nov 2, 2017 at 1:10 PM, Mohammed Naser
<mna...@vexxhost.com<mailto:mna...@vexxhost.com>> wrote:
> On Thu, Nov 2, 2017 a
0 ERROR nova.api.openstack.compute.floating_ips
ConnectTimeout: Request to
https://127.0.0.1:9696/v2.0/floatingips/2e3fa334-d6ac-443c-b5ba-eeb521d6324c
timed out
Nova compute API properly running with wsgi under apache2? And nova metadata
API running under the nova-api process?
Yea, must
it manually.
The apache2 mod_wsgi config should be OK according to the docs [1].
Best regards
[1]
http://modwsgi.readthedocs.io/en/develop/configuration-directives/WSGIDaemonProcess.html
On 11/14/2017 11:12 AM, Jens Harbott wrote:
> 2017-11-14 8:24 GMT+00:00 Tobias Urdin <tobias.ur...@crysto
I've been staring at this for almost an hour now going through all the logs and
I can't really pin a point from
where that error message is generated. Cannot find any references for the timed
out message that the API returns or the unable to associate part.
What I'm currently staring at is
I got started on kuryr-libnetwork but never finished the init/systemd scripts
but all dependencies in control file should be ok.
I uploaded it here: https://github.com/tobias-urdin/deb-kuryr-libnetwork (not a
working package!)
After fixing kuryr-libnetwork one can get starting packaging Zun
Hello,
I was very interested in packaging Zun for Ubuntu however I did not have the
time to properly get started.
I was able to package kuryr-lib, I've uploaded it here for now
https://github.com/tobias-urdin/deb-kuryr-lib
Would love to see both Zun and Qinling in Ubuntu to get a good grip
Hello,
I was interested in getting Magnum working in gate by getting @dms patch
fixed and merged [1].
The installation goes fine on Ubuntu and CentOS however the tempest
testing for Magnum fails on CentOS (it not available in Ubuntu).
It seems to be related to authentication against keystone
Hello CloudKitty team,
I'm having an issue with this review not going through and being stuck after
staring at it for a while now [1].
Is there any configuration[2] issue that are causing the error[3]? Or is the
package broken?
Thanks for helping out!
Best regards
[1]
the above.
Best regards
On 06/19/2018 12:35 AM, Alex Schultz wrote:
> On Mon, Jun 18, 2018 at 4:08 PM, Tobias Urdin
> wrote:
>> Hello CloudKitty team,
>>
>>
>> I'm having an issue with this review not going through and being stuck after
>> staring at it for
Hello everybody,
I'm cross-posting this with operators list.
The openvswitch flows-based stateful firewall driver which uses the
conntrack support in Linux kernel >= 4.3 (iirc) has been
marked as experimental for several releases now, is there any
information about flaws in this and why it should
We are using them for one of our deployments and are working on moving
our other one to use the same modules :)
Best regards
On 06/04/2018 11:06 PM, Arnaud Morin wrote:
> Hey,
>
> OVH is also using them as well as some custom ansible playbooks to manage the
> deployment. But as for red had,
Great work Thomas!
We also got a good overview on some challenges and issues regarding
moving to python3 support for the Puppet modules in the future.
But we can easily state that the main work will lay with making sure
there is python3 supported distro packages.
Which you with Debian python3
Maybe loop in the neutron and/or Canonical OpenStack team on this one.
Best regards
Tobias
____
From: Tobias Urdin <tobias.ur...@crystone.com>
Sent: Friday, December 22, 2017 2:44 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject
On 02/15/2018 08:52 PM, Matthew Thode wrote:
> On 18-02-15 13:38:45, Matthew Thode wrote:
>> On 18-02-15 09:31:19, Thomas Goirand wrote:
>>> Hi,
>>>
>>> Since I'm getting some pressure from other DDs to actively remove Py2
>>> support from my packages, I'm very much considering switching all of
Follow up on Alex[1] point. The db sync upgrade for neutron fails here[0].
[0] http://paste.openstack.org/show/629628/
On 12/22/2017 04:57 AM, Alex Schultz wrote:
>> Just a note, the queens repo is not currently synced in the infra so
>> the queens repo patch is failing on Ubuntu jobs. I've
/networking-l2gw/refs/
[3] https://review.openstack.org/#/c/529711/
On 12/22/2017 10:19 AM, Tobias Urdin wrote:
> Follow up on Alex[1] point. The db sync upgrade for neutron fails here[0].
>
> [0] http://paste.openstack.org/show/629628/
>
> On 12/22/2017 04:57 AM, Alex Schultz wrote:
)
* Disable l2gw because of
https://bugs.launchpad.net/ubuntu/+source/networking-l2gw/+bug/1739779
proposed temp fix until resolved as [1]
[0] https://review.openstack.org/#/c/507925/
[1] https://review.openstack.org/#/c/529830/
Best regards
On 12/22/2017 10:44 AM, Tobias Urdin wrote:
> Ign
Hello,
I'm testing around with Magnum and have so far only had issues.
I've tried deploying Docker Swarm (on Fedora Atomic 27, Fedora Atomic
28) and Kubernetes (on Fedora Atomic 27) and haven't been able to get it
working.
Running Queens, is there any information about supported images? Is
Hello Stackers,
I'm submitting myself as PTL candidate for the Puppet OpenStack project. [0]
I've been active in the OpenStack community since late 2014 early 2015
and have had a lot of focus on the
Puppet OpenStack project since about 2016. I've been a core reviewer for
about five months now
Hello all Puppeters,
We are approaching the PTG in Denver and want to remind everybody to make sure
you book your accommodations because they will run out.
I've created an etherpad here [1] where you can add any topic you want to
discuss.
I will not be able to attend the PTG, if we get any
Hello all incredible Puppeters,
I've tested setting up an Storyboard instance and test migrated
puppet-ceph and it went without any issues there using the documentation
[1] [2]
with just one minor issue during the SB setup [3].
My goal is that we will be able to swap to Storyboard during the
to kick off
the script once the change merges.
-Kendall (diablo_rojo)
On Tue, Aug 14, 2018 at 9:33 AM Tobias Urdin <mailto:tobias.ur...@binero.se>> wrote:
Hello all incredible Puppeters,
I've tested setting up an Storyboard instance and test migrated
puppet-ceph and it wen
.org/#%21/project_group/60>
On Wed, Aug 15, 2018 at 12:08 AM Tobias Urdin <mailto:tobias.ur...@binero.se>> wrote:
Hello Kendall,
Thanks for your reply, that sounds awesome!
We can then dig around and see how everything looks when all
project bugs are imported to stories.
Hello all Puppeteers!
Welcome to the weekly Puppet recap for week 33.
This is a weekly overview of what has changed in the Puppet OpenStack
project the past week.
CHANGES
Changes in all modules
---
*
ise-client-urls="${ETCD_ADVERTISE_CLIENT_URLS}"
--cert-file="${ETCD_PEER_CERT_FILE}" --key-file="${ETCD_PEER_KEY_FILE}"
Makes it work, any thoughts?
Best regards
Tobias
On 08/23/2018 03:54 PM, Tobias Urdin wrote:
Found the issue, I assume I have to use Fedora Atomic 26 until Rock
are removed
from the base image.)
https://review.openstack.org/#/c/524116/ (Run etcd and flanneld in a
system container)
Still wondering about the "The Parameter (nodes_affinity_policy) was not
provided" when using Mesos + Ubuntu?
Best regards
Tobias
On 08/23/2018 02:56 PM, Tobias U
-stein
Wishing you all a great weekend!
Best regards
Tobias (tobias-urdin @ IRC)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
Hello Kendall,
I think you can just leave them in the group then, at your convenience.
If they are there we can start using them if so.
Best regards
Tobias
On 08/17/2018 11:08 PM, Kendall Nelson wrote:
On Fri, Aug 17, 2018 at 12:15 AM Tobias Urdin <mailto:tobias.ur...@binero.se>&
on the standby router?
Best regards
Tobias
On 08/20/2018 11:37 AM, Tobias Urdin wrote:
Forgot [neutron] tag.
On 08/20/2018 11:36 AM, Tobias Urdin wrote:
Hello,
Note: before reading, this router was a regular router but was then
disable, changed ha=true so it's now a L3 HA router
router?
Best regards
On 08/20/2018 11:50 AM, Tobias Urdin wrote:
Ok, so the issue here seems to be that I have a L3 HA router with
SLAAC, both the active and standby router will
configure the SLAAC obtained address causing a conflict since both
side share the same MAC address.
Is there any
?
Best regards
Tobias
On 08/20/2018 11:58 AM, Tobias Urdin wrote:
Continuing forward, these patches should've fixed that
https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged)
I'm on Queens.
The two inside interfaces on the backup router:
[root@controller2 ~]# ip
Hello,
Note: before reading, this router was a regular router but was then
disable, changed ha=true so it's now a L3 HA router, then it was enabled
again.
CC openstack-dev for help or feedback if it's a possible bug.
I've been testing around with IPv6 and overall the experience has been
Forgot [neutron] tag.
On 08/20/2018 11:36 AM, Tobias Urdin wrote:
Hello,
Note: before reading, this router was a regular router but was then
disable, changed ha=true so it's now a L3 HA router, then it was
enabled again.
CC openstack-dev for help or feedback if it's a possible bug.
I've
Hello,
Requesting reviews from the magnum-ui core team for
https://review.openstack.org/#/c/595245/
I'm hoping that we could make quick due of this and be able to backport
it to the stable/rocky release, would be ideal to backport it for
stable/queens as well.
Best regards
Tobias
gress and a bit hacky:
https://github.com/cybera/magnum-templates
Hope that helps,
Joe
On Fri, Aug 3, 2018 at 6:46 AM, Tobias Urdin <mailto:tobias.ur...@binero.se>> wrote:
Hello,
I'm testing around with Magnum and have so far only had issues.
I've tried deploying Docker Swarm
Hello Stackers,
Would just like to give a heads-up that the puppet-openstack project as
of the Rocky release will supports
Ubuntu 18.04 Bionic and we are as of yesterday/today checking that in
infra Zuul CI.
As a step for adding this support we also introduced support for the
Ceph Mimic release
Emilien,
You've been an inspiration to the community and to me personally!
Thanks for helping making OpenStack better in all aspects.
Best regards
Tobias
On 09/05/2018 04:15 AM, Emilien Macchi wrote:
After 2 years at the TC, I feel lucky enough to have been part of this
group where I hope
Hello fellow Puppeteers!
Welcome to the weekly Puppet recap for week 35 and 36.
Because I was away last week I forgot to follow up the progress of week 35.
The past two weeks has been quite calm, we have had a lot of changes due
to the move
away from Zuul config in project-config and the bump
Hello Doug,
I've proposed moving all job config from project-config to the repos [1].
I don't know what to do with the periodic job here [2] should that be
left in project-config or moved?
Best regards
Tobias
[1] https://review.openstack.org/#/q/topic:move-zuul-config
[2]
Oh, that's bad. I will abandon.
It's a go for Puppet then.
Best regards
On 08/31/2018 12:36 PM, Andreas Jaeger wrote:
On 2018-08-31 10:49, Tobias Urdin wrote:
Hello Doug,
I've proposed moving all job config from project-config to the repos [1].
I don't know what to do with the periodic job
Hello Alex,
I personally don't know about any entity specifically working on the Puppet
Senlin module.
We strongly welcome anybody to contribute to the development of the Puppet
OpenStack modules.
We are happy to help :)
Best regards
Tobias
Sent from my iPhone
On 9 Jul 2018, at 16:00,
Two different setups, very basic.
AggregateInstanceExtraSpecsFilter
RetryFilter
AvailabilityZoneFilter
ComputeFilter
ComputeCapabilitiesFilter
ImagePropertiesFilter
ServerGroupAntiAffinityFilter
ServerGroupAffinityFilter
RetryFilter
AvailabilityZoneFilter
RamFilter
ComputeFilter
got the "invalid padding" issue it was because of the DN I used
for the CA and the certificate IIRC.
> 19:34 < tobias-urdin> 2018-09-10 19:43:15.312 15032 WARNING
octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect
to instance. Retrying.: SSLError: (&q
+operators
My bad.
On 10/22/2018 10:22 AM, Tobias Urdin wrote:
Hello,
I've been having a lot of issues with SSL certificates myself, on my
second trip now trying to get it working.
Before I spent a lot of time walking through every line in the DevStack
plugin and fixing my config options
at 4:23 AM Tobias Urdin wrote:
Hello,
I've been having a lot of issues with SSL certificates myself, on my
second trip now trying to get it working.
Before I spent a lot of time walking through every line in the DevStack
plugin and fixing my config options, used the generate
script [1] and still
hake which caused our issue.
After going through the whole stack, we have Octavia working flawlessly
without any issues at all.
Best regards
Tobias
On 10/23/2018 04:31 PM, Tobias Urdin wrote:
Hello Erik,
Could you specify the DNs you used for all certificates just so that I
can rule it out on my
Hello,
Due to bugs and fixes that has been needed we are probably going to
merge some changes to
Puppet modules which will cause a refresh of their services meaning they
will be restarted.
If you are following the stable branches (stable/rocky in this case) and
not using tagged releases
Thanks Sean!
I did a quick sanity check on the backup part in the puppet-cinder
module and there is no opinionated
default value there which needs to be changed.
Best regards
On 09/27/2018 08:37 PM, Sean McGinnis wrote:
This probably applies to all deployment tools, so hopefully this
:18 AM Tobias Urdin wrote:
Hello,
We've been talking for a while about the deprecation and removal of the
stable/newton branches.
I think it's time now that we get rid of them, we have no open patches
and Newton is considered EOL.
Could cores get back with a quick feedback and then the stable
Hello,
We've been talking for a while about the deprecation and removal of the
stable/newton branches.
I think it's time now that we get rid of them, we have no open patches
and Newton is considered EOL.
Could cores get back with a quick feedback and then the stable team can
get rid of
Sounds great, thanks for pushing this Emilien!
Best regards
Tobias
On 09/15/2018 07:48 PM, Emilien Macchi wrote:
I'm currently taking care of creating puppet-placement:
https://review.openstack.org/#/c/602870/
https://review.openstack.org/#/c/602871/
https://review.openstack.org/#/c/602869/
56 matches
Mail list logo
