Good to know - thanks for that.
On 4/9/20, 11:04 AM, "Chris Milne" <cmilne(a)mailfence.com> wrote:
So just an update on the SSH provisioning. I tried "Customized Linux"
for the Platform and that didn't work.
Then I tried your other suggestion of "Aliyun Linux" and suddenly it was
accepting SSH connections (previously no SSH was working at all).
However it was still prompting for a password, despite the SSH
negotiation offering my key.
So then instead I tried `ssh aliyun@serverip` and lo and behold that
Basically it seems that the admin user is called "aliyun" instead of
"clear" as in the case of AWS.
I see that now looking at the src of ucd-data-fetch.c
The image is supposed to be provisioned to have the `clear` user that
can remotely access the machine using the SSH key you provided. That
is how micro-config-drive works for all these cloud cases. (AWS etc
work this way).
The user gets created dynamically at boot. You can even manually run
this after boot and test it: `/usr/bin/ucd-data-fetch aliyun` as root
should work. It also may provide some debug output explaining why it
didn't create the `clear` user.
On 4/8/20 1:06 PM, Chris Milne wrote:
> No worries. I might try a Customized or Aliyun Platform choice for
> the next instance and see how that goes. Will report back if find
> anything interesting 😀
> On a side note noticed this Ali image is slightly different from the
> AWS one in at least one respect. That is it has a "root" user for
> doing admin type things, whereas the AWS uses "clear" as a superuser.
> Was thinking of adding a "clear" user to keep things consistent,
> though didn't know if there any edge cases I might miss doing so.
> Guessing the idea behind the "clear" admin user is better security
> and foot gun protection for noobs like myself :p
> On 4/7/20 5:10 PM, Auke Kok wrote:
>> I didn't get a reply back from one of our engineers who I worked
>> with to enable micro-config-drive for Aliyun a while back. It is
>> supposed to pick up the SSH key through a normal openstack-like HTTP
>> fetch over IP (see https://github.com/clearlinux/micro-config-drive
>> - for more info) and plant it in place. It's possible that indeed
>> it's just as simple as choosing the right OS here would work
>> (Customized Linux? Maybe even Aliyun?!).
>> Glad it's working though!
>> On 4/5/20 7:46 PM, Chris Milne wrote:
>>> This is great. I was able to get it up and running with the new
>>> 32750 image you sent over.
>>> The "ssh-key on instance install" didn't kick in, but
>>> Just manually enabled root login for ssh (/etc/ssh/sshd_config) via
>>> the web console and went from there to get keys copied over.
>>> The SSH install issue might be related to the image wizard. When I
>>> was importing the custom image Aliyun asked me too specify the
>>> Platform (a required field). Options were, CentOS, Ubuntu, CoreOS,
>>> Aliyun, Debian, SUSE, OpenSUSE, FreeBSD, RedHat, Others Linux,
>>> Customized Linux. I chose "Others Linux", but not sure it even
>>> Haven't had a chance yet to test everything with required installs
>>> (python, etc), though so far it's looking promising
>>> Thanks again for the help :)
>>> On 4/5/20 1:27 PM, Nesius, Robert A wrote:
>>>>> On Apr 5, 2020, at 8:41 AM, Chris Milne <cmilne(a)mailfence.com>
>>>>> Ahh. Thanks for the additional context.
>>>>> Rolling a custom image may indeed be beyond my pay grade. Perhaps
>>>>> best then to wait and see what team come back with.
>>>>> Obviously CL would be first prize because it's so performant,
>>>>> minimalist and, and, and, Ok fine, I'll stop gushing ;)
>>>>> That said, it sounds like running on Aliyun may or may not be a
>>>>> priority right now, so not getting hopes up just yet.
>>>> We do produce an Aliyun image, but it was based on requirements
>>>> given to us from our colleagues over there and we don’t have
>>>> validation of that image in our daily release activities.
>>>> Consequently we don’t advertise it along with the rest of our
>>>> validated images.
>>>> But you could give it a try and let us know if it works:
>>>> If this works but would like an image baked differently you can
>>>> modify the config file and use clr-installer to make your own.
>>> Dev mailing list -- dev(a)lists.clearlinux.org
>>> To unsubscribe send an email to dev-leave(a)lists.clearlinux.org