[Fiware-webui] Using the chef server for testing

[Philipp Slusallek]

Hi,

Great Torsten! It probably makes sense to put this description
somewhere, where people can find it. Maybe in this or next weeks minutes
of our call?


Thanks,

	Philipp

Am 28.10.2014 um 10:48 schrieb Torsten Spieldenner:
> Hi,
> 
> let's see if I remember all the steps that I have thaken there.
> 
> I requested accounts on both chef testserver (130.206.81.105) and chef
> cloud portal (130.206.81.61). I have received separate credentials for
> both and a private key for the user that was created on testserver (.105)
> 
> Having created the recipes, I uploaded them to the SVN that is specified
> on the Wikipage. After a while, the recipe appeared under the
> "Cookbooks"-tabs in the chef testserver GUI (.105).
> 
> In the testserver GUI (. . .105), I created a node by switching to the
> "Nodes" tab and selecting "Create". For the newly created node, I could
> specify a runlist by dragging-and-dropping recipes from the list of all
> recipes.
> 
> Moreover I  created a "Client" in the "Clients" tab the same way. This
> should give you a private key that you can copy to your cloud instance
> and specify in your chef config there. We'll come to this later.
> 
> Now I created an instance in the Cloud Portal (. . .61). The image that
> is suggested in the Wiki did not exists, but as Erno pointed out some
> time ago, the "Ubuntu-chef" image worked. I created a security group
> with all necessary ports open (SSH , HTTP ), assigned this, created a
> public IP and connected via SSH. On the cloud instance, I did run knife
> config as given in the Wiki.
>  Somehow, specifying the values via knife did not work for me, but I
> could perform configuration by editing the file "client.rb" which is
> located in the /etc/chef folder.
> 
> I have entered the following values:
> 
>  ssl_verify_mode                :verify_none
>  validation_client_name    "chef-validator"
>  validation_key                    "/etc/chef/validation.pem"
>  client_key                            "/etc/chef/client.pem" [The
> private key which I received for my client that I created on the test
> server]
>  chef_server_url                   "https://130.206.81.105"
>  node_name                         "[Name of my previously created node]"
> 
> When I now run "chef-client", it connects to my specified node and
> executes the run-list that I have assembled in the test-server gui.
> 
> I guess that was all I did, and for me, it works.
> 
> Hope that helps
> 
> Best,
> Torsten
> 
> Am 10/28/2014 9:29 AM, schrieb "Lasse Öörni":
>> Hi,
>> just a brief heads-up from Ludo's side: Jonne V. will be taking over the
>> remaining packaging activities for Ludo's GE's.
>>
>> Related to that: we'd appreciate a writeup from someone who successfully
>> managed to test their recipes at https://130.206.81.105: what client
>> image
>> did you use, and at which point did you need the .pem file received from
>> Henar related to your account at 130.206.81.105 etc.
>>
>> Last time I tried the chef-client refused to connect to the server,
>> citing
>> permission problem. The related section on the FIWARE wiki page
>>
>> (https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_create_recipes_for_the_GEs)
>>
>>
>> just states
>>
>> "Once you have deployed the VM, enter in the VM, and execute chef-client.
>> This process will register your VM into the chef-server."
>>
> 
> 


-- 

-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern

Geschäftsführung:
  Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
  Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
  Prof. Dr. h.c. Hans A. Aukes

Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973, Steuernummer:  19/673/0060/3
---------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: philipp_slusallek.vcf
Type: text/x-vcard
Size: 441 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-webui/attachments/20141029/a0aa88d0/attachment.vcf>