On Fri, Apr 7, 2017 at 2:27 PM, Andreas Jaeger wrote:
> On 2017-04-07 18:55, Emilien Macchi wrote:
>> os-cloud-config has been retired in Infra and in the repo.
>> RDO packaging has also been updated.
>> Now waiting for final approval in Governance:
>> https://review.openstack.org/#/c/451096/
>>
>
On 2017-04-07 18:55, Emilien Macchi wrote:
> os-cloud-config has been retired in Infra and in the repo.
> RDO packaging has also been updated.
> Now waiting for final approval in Governance:
> https://review.openstack.org/#/c/451096/
>
> If bug fixes has to happen, please submit to stable branches
os-cloud-config has been retired in Infra and in the repo.
RDO packaging has also been updated.
Now waiting for final approval in Governance:
https://review.openstack.org/#/c/451096/
If bug fixes has to happen, please submit to stable branches directly
and let us know on #rdo, we'll update the pin
The retirement patch is ready whenever you are:
https://review.openstack.org/#/c/450946/
Please review.
Thanks,
On Mon, Apr 3, 2017 at 3:53 AM, Bogdan Dobrelya wrote:
> On 31.03.2017 13:58, Jiří Stránský wrote:
>> On 30.3.2017 17:39, Juan Antonio Osorio wrote:
>>> Why not drive the post-config
On 31.03.2017 13:58, Jiří Stránský wrote:
> On 30.3.2017 17:39, Juan Antonio Osorio wrote:
>> Why not drive the post-config with something like shade over ansible?
>> Similar to what the kolla-ansible community is doing.
>
> We could use those perhaps, if they bring enough benefit to add them to
>
On 30.3.2017 17:39, Juan Antonio Osorio wrote:
Why not drive the post-config with something like shade over ansible?
Similar to what the kolla-ansible community is doing.
We could use those perhaps, if they bring enough benefit to add them to
the container image(s) (i think we'd still want to
On 30.3.2017 18:02, Bogdan Dobrelya wrote:
On 30.03.2017 15:40, Jiří Stránský wrote:
What might be interesting is solving the keystone init within containers
along with our container entrypoint situation. We've talked earlier that
we may have to build our custom entrypoints into the images as w
On 30.03.2017 15:40, Jiří Stránský wrote:
>
> What might be interesting is solving the keystone init within containers
> along with our container entrypoint situation. We've talked earlier that
> we may have to build our custom entrypoints into the images as we
> sometimes need to do things that t
On Thu, Mar 30, 2017 at 6:58 AM, Dan Prince wrote:
> There is one case that I was thinking about reusing this piece of code
> within a container to help initialize keystone endpoints. It would
> require some changes and updates (to match how puppet-* configures
> endpoints).
>
> For TripleO contai
Why not drive the post-config with something like shade over ansible?
Similar to what the kolla-ansible community is doing.
On 30 Mar 2017 16:42, "Jiří Stránský" wrote:
> On 30.3.2017 14:58, Dan Prince wrote:
>
>> There is one case that I was thinking about reusing this piece of code
>> within a
On 30.3.2017 14:58, Dan Prince wrote:
There is one case that I was thinking about reusing this piece of code
within a container to help initialize keystone endpoints. It would
require some changes and updates (to match how puppet-* configures
endpoints).
For TripleO containers we use various pup
There is one case that I was thinking about reusing this piece of code
within a container to help initialize keystone endpoints. It would
require some changes and updates (to match how puppet-* configures
endpoints).
For TripleO containers we use various puppet modules (along with hiera)
to drive
Hi,
os-cloud-config was deprecated in the Ocata release and is going to be
removed in Pike.
TripleO project doesn't need it anymore and after some investigation
in codesearch.openstack.org, nobody is using it in OpenStack.
I'm working on the removal this cycle, please let us know any concern.
Th
Hello everyone,
A new release candidate for os-cloud-config for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/os-cloud-config/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello,
we call it from UI after the deployment
https://github.com/openstack/tuskar-ui/blob/master/tuskar_ui/infrastructure/overview/forms.py#L222
.
There should be conversation on the summit whether to do the call from
somewhere else (tuskar, template..).
Kind Regards,
Ladislav
On 10/30/20
Dear all,
Seems like os-cloud-config is to initialise uncercloud or overcloud after heat
orchestration. But I can not find how it is used in either tuskar, or
tuskar-UI. So can anyone explain a little bit how it is used in TripleO
projects? Thanks.
Best RegardsLeslie Wang
(Removing [Heat] from the subject.)
So here are the steps i think are necessary to get the PKI setup done
and safely passed through Jenkins. If anyone thinks something is
redundant or missing, please shout:
1. Patch to os-cloud-config:
* Generation of keys and certs for cases user doesn't
Excerpts from Adam Young's message of 2014-03-12 06:19:47 -0700:
> On 03/11/2014 01:20 PM, Clint Byrum wrote:
> > Excerpts from Adam Young's message of 2014-03-11 07:50:58 -0700:
> >> On 03/11/2014 05:25 AM, Dmitry Mescheryakov wrote:
> >>> For what it's worth in Sahara (former Savanna) we inject t
On 11.3.2014 15:50, Adam Young wrote:
On 03/11/2014 05:25 AM, Dmitry Mescheryakov wrote:
For what it's worth in Sahara (former Savanna) we inject the second
key by userdata. I.e. we add
echo "${public_key}" >> ${user_home}/.ssh/authorized_keys
to the other stuff we do in userdata.
Dmitry
2014
On 03/11/2014 01:20 PM, Clint Byrum wrote:
Excerpts from Adam Young's message of 2014-03-11 07:50:58 -0700:
On 03/11/2014 05:25 AM, Dmitry Mescheryakov wrote:
For what it's worth in Sahara (former Savanna) we inject the second
key by userdata. I.e. we add
echo "${public_key}" >> ${user_home}/.s
Excerpts from Jiří Stránský's message of 2014-03-10 06:10:46 -0700:
> On 7.3.2014 14:50, Imre Farkas wrote:
> > On 03/07/2014 10:30 AM, Jiří Stránský wrote:
> >> Hi,
> >>
> >> there's one step in cloud initialization that is performed over SSH --
> >> calling "keystone-manage pki_setup". Here's the
Excerpts from Adam Young's message of 2014-03-11 07:50:58 -0700:
> On 03/11/2014 05:25 AM, Dmitry Mescheryakov wrote:
> > For what it's worth in Sahara (former Savanna) we inject the second
> > key by userdata. I.e. we add
> > echo "${public_key}" >> ${user_home}/.ssh/authorized_keys
> >
> > to the
On 03/11/2014 05:25 AM, Dmitry Mescheryakov wrote:
For what it's worth in Sahara (former Savanna) we inject the second
key by userdata. I.e. we add
echo "${public_key}" >> ${user_home}/.ssh/authorized_keys
to the other stuff we do in userdata.
Dmitry
2014-03-10 17:10 GMT+04:00 Jiří Stránský :
For what it's worth in Sahara (former Savanna) we inject the second
key by userdata. I.e. we add
echo "${public_key}" >> ${user_home}/.ssh/authorized_keys
to the other stuff we do in userdata.
Dmitry
2014-03-10 17:10 GMT+04:00 Jiří Stránský :
> On 7.3.2014 14:50, Imre Farkas wrote:
>>
>> On 03/0
On Mon, Mar 10, 2014 at 6:10 AM, Jiří Stránský wrote:
> On 7.3.2014 14:50, Imre Farkas wrote:
>>
>> On 03/07/2014 10:30 AM, Jiří Stránský wrote:
>>>
>>> Hi,
>>>
>>> there's one step in cloud initialization that is performed over SSH --
>>> calling "keystone-manage pki_setup". Here's the relevant c
On 7.3.2014 14:50, Imre Farkas wrote:
On 03/07/2014 10:30 AM, Jiří Stránský wrote:
Hi,
there's one step in cloud initialization that is performed over SSH --
calling "keystone-manage pki_setup". Here's the relevant code in
keystone-init [1], here's a review for moving the functionality to
os-cl
On 03/07/2014 10:30 AM, Jiří Stránský wrote:
Hi,
there's one step in cloud initialization that is performed over SSH --
calling "keystone-manage pki_setup". Here's the relevant code in
keystone-init [1], here's a review for moving the functionality to
os-cloud-config [2].
The consequence of thi
Hi,
there's one step in cloud initialization that is performed over SSH --
calling "keystone-manage pki_setup". Here's the relevant code in
keystone-init [1], here's a review for moving the functionality to
os-cloud-config [2].
The consequence of this is that Tuskar will need passwordless ss
28 matches
Mail list logo
