If I understand correctly, we currently deploy a web server on port 8080 on
the VR and send a specially crafted request to retrieve the password.
This requires special made scripts or software on the guest vms to execute
the password reset.
At the same time cloud-init has become the de facto stan
ot;
> To: "dev"
> Sent: Tuesday, 26 August, 2014 9:34:44 PM
> Subject: [DISCUSS] Changing the way password reset works, or allowing the
> cloud-init way
>
> If I understand correctly, we currently deploy a web server on port 8080 on
> the VR and send a specially craf
On Tue, Aug 26, 2014 at 11:44 PM, Nux! wrote:
> Hi Erik and thanks for your effort. Using user data is a nice idea.
> Let's see what more experienced programmers have to say on this.
>
>
Sure thing
One thing that I noticed; though it might have been OK in your particular
> case, "rm -rf /var/lib
I'm wondering how you keep the root password secure. Right now, it works
similarly to userdata and metadata, in that the instance queries its router
as it boots, but then the password is wiped once queried. If this didn't
happen, non-root users could query for the root password all day. Do you
sugg
On Tue, Aug 26, 2014 at 3:04 PM, Marcus wrote:
> I'm wondering how you keep the root password secure. Right now, it works
> similarly to userdata and metadata, in that the instance queries its router
> as it boots, but then the password is wiped once queried. If this didn't
> happen, non-root use
Yeah, that would be low hanging fruit as far as features go, since the API
is already in place to set VM public keys.
On Tue, Aug 26, 2014 at 4:33 PM, Carlos Reategui
wrote:
> On Tue, Aug 26, 2014 at 3:04 PM, Marcus wrote:
>
> > I'm wondering how you keep the root password secure. Right now, i
On Aug 26, 2014, at 1:34 PM, Erik Weber wrote:
> If I understand correctly, we currently deploy a web server on port 8080 on
Slight correction: A processes on the VR listens on port 8080, and hands any
connections to a UNIX script. Calling it a "web server" is way too kind.
Also, you’re just l
@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Subject: Re: [DISCUSS] Changing the way password reset works, or allowing the
cloud-init way
On Aug 26, 2014, at 1:34 PM, Erik Weber
mailto:terbol...@gmail.com>> wrote:
If I understand cor
;>
> Date: Tuesday, August 26, 2014 at 4:04 PM
> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> Subject: Re: [DISCUSS] Changing the way password reset works, or allowing
> the cloud-ini
On Wed, Aug 27, 2014 at 1:04 AM, John Kinsella wrote:
>
> On Aug 26, 2014, at 1:34 PM, Erik Weber wrote:
> > If I understand correctly, we currently deploy a web server on port 8080
> on
>
> Slight correction: A processes on the VR listens on port 8080, and hands
> any connections to a UNIX scri
On Wed, Aug 27, 2014 at 4:47 AM, Marcus wrote:
> We had set up an agent in the VM that listens on the virtio serial port,
> similar to how the virtual router gets its configurations now in KVM. Host
> to guest communication is an option, and is fairly standardized (qemu guest
> agent, VMware tool
che.org<mailto:dev@cloudstack.apache.org>"
> mailto:dev@cloudstack.apache.org>>
> Subject: Re: [DISCUSS] Changing the way password reset works, or allowing the
> cloud-init way
>
>
> On Aug 26, 2014, at 1:34 PM, Erik Weber
> mailto:terbol...@gmail.com>> wrote
rg>>
Date: Tuesday, August 26, 2014 at 4:04 PM
To:
"dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org>"
<
dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org>>
Subject: R
13 matches
Mail list logo
