Regarding Synnefo environment provider for Juju

[Thodoris Sotiropoulos]

I checked the entries of the database after the error. Specifically, 
this is the document for the Model collection.

[
     {
         "_id" : "d96ef8ae-36ca-4af7-870f-7914d844df68",
         "life" : 0,
         "migration-mode" : "",
         "name" : "test",
         "owner" : "admin at local",
         "server-uuid" : "d96ef8ae-36ca-4af7-870f-7914d844df68",
         "txn-queue" : [
             "575e976cba3f0466055d8654_fff99943",
             "575e976fba3f0466055d865a_33f7ddf5"
         ],
         "txn-revno" : NumberLong(2)
     }
]

Therefore, there is already one record (this is the controller model, 
right?) on db before the command `err = newState.runTransaction(ops) ` 
on `state/model.go` line 192 runs.
Is the error associated with the name of the controller model? I imagine 
that it shouldn't be named "test", right?


Thodoris

On 06/13/2016 01:33 AM, Tim Penhey wrote:
> Hi Thodoris,
>
> I had a quick look through the current code in the branch, and nothing 
> is obvious there.
>
> What is the command line that you are running?
>
> The failure is due to the database already thinking there is a model 
> that exists for the same user with the same name. Although now what we 
> normally create is two models on bootstrap:
>  * controller - where the machines running Juju live (apiserver and db)
>  * default - where the user is left to deploy workloads.
>
> The error is that the model name is "test". This shouldn't be the case 
> as the database should be empty.
>
> Tim
>
> On 08/06/16 23:28, Thodoris Sotiropoulos wrote:
>> Hi all,
>>
>> You may remember previous e-mails sent by my partner Stavros Sachtouris
>> regarding
>> the case of implementing a Juju environment provider for our open source
>> IaaS called
>> Synnefo.
>>
>> We have started implementation of the basics (configuration schema,
>> instance creation,
>> instance queries, preparation of environment, etc). Our goal is to make
>> a proof
>> of concept implementation of the bootstrap command and that's why we
>> have ignored
>> networking and storage configuration, a.k.a mocked.
>>
>> So far, we have managed to create and communicate with a machine
>> instance. However,
>> during the last step of bootstrap process (insertion of the admin model
>> to database)
>> we are facing an unexpected problem (method `NewModel` of
>> `state/model.go`).
>>
>> Here is the corresponding log file:
>> https://pithos.okeanos.grnet.gr/public/8EHM5jpEm2W7bSwly9wFG
>>
>> I tried to investigate the problem but I cannot figure out why I get the
>> `model %s for %q already exists`. What am I missing? I would 
>> appreciate any
>> help or guidance.»
>>
>> Thank you in advance
>>
>> Thodoris Sotiropoulos
>> Developer @ GRNET
>> theosot at grnet.gr
>>