Open laszewsk opened 5 years ago
Does this happen with cloudmesh-installer
?
I think what happens if we do
cloudmesh-installer install cms
the dir gets created but not yet cloudmesh.yaml
then wen we say
cloudmesh-installer install cloud
the .cloudmesh dir is already there and the yaml file does not created.
so we need to check if the yaml file is not there and if not create it and not check for dir.
I have not yet verified this.
I just tested this on windows:
cloudmesh-installer git clone cms
cloudmesh-installer install cms -e
cms help
at this point there is no cloudmesh.yaml file. Then I continued:
cloudmesh-installer git clone cloud
cloudmesh-installer install cloud -e
at this point there is no cloudmesh.yaml file either. Then I continued:
cms help
And then the cloumesh.yaml was created. Isn't this expected?
Yes, so this all works correctly ;-=)
I think what we have is a documentation issue that
Cms help needs to be called a second time
Maybe we need to implement a
Cms setup cloud Or Cms cloud setup command that simply calls cos help so we have an easier time to remember and document ;-)
Not yet sure, maybe we even have such a command already ...
On Sep 14, 2019, at 11:16 AM, Vafa Andalibi notifications@github.com wrote:
I just tested this on windows:
cloudmesh-installer git clone cms cloudmesh-installer install cms -e cms help at this point there is no cloudmesh.yaml file. Then I continued:
cloudmesh-installer git clone cloud cloudmesh-installer install cloud -e at this point there is no cloudmesh.yaml file either. Then I continued:
cms help And then the cloumesh.yaml was created. Isn't this expected?
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/cloudmesh/cloudmesh-cloud/issues/229?email_source=notifications&email_token=AADHYVIZA632ZFV5FISRE3TQJT53RA5CNFSM4IWSMYFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6W5XKY#issuecomment-531487659, or mute the thread https://github.com/notifications/unsubscribe-auth/AADHYVNZWQWIJX5G7M3TKILQJT53RANCNFSM4IWSMYFA.
I see , Should this issue be closed then?
No we need to document this better in the manual,
And think about a command
"cms init yaml” or cms yaml init ?
Or locate if we have such a command, I remember vaguely I implemented such a thing, but I can not remember anymore the command name or if it was in a previous version fo cloudmesh.
On Sep 15, 2019, at 8:59 AM, Vafa Andalibi notifications@github.com wrote:
I see , Should this issue be closed then?
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/cloudmesh/cloudmesh-cloud/issues/229?email_source=notifications&email_token=AADHYVPDGJ4Q6KYOZFHGRQTQJYWU7A5CNFSM4IWSMYFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XQILY#issuecomment-531563567, or mute the thread https://github.com/notifications/unsubscribe-auth/AADHYVLGLATOFP3SQNFMZ3TQJYWU7ANCNFSM4IWSMYFA.
There was an issue in cms init that the keys were not properly loaded and uploaded to the cloud. This has been fixed, but I am not sure if we have a comprehensive test for this that works on other clouds.
looks like when we install cloudmesh new and end up at cms help the cloudmesh.yaml file is not created.
this happens when we install bundle cms
does this also happen when we install cloudmesh-cloud.
if so this seems a bug
We found there was a bug in the config based on windows, but we did not test the deployment on windows
We found it is a documentation bug