[Container-tools] CDK Server Adapter - First Demo

[Langdon White]

Langdon
Platform Architect

From: Pete Muir
Sent: Nov 4, 2015 6:21 AM
To: Rob Stryker
Cc: developer-tooling at redhat.com; container-tools
Subject: Re: CDK Server Adapter - First Demo

The update to the vagrant-registration plugin changed the 
configuration parameter names: Try 


config.registration.username = "#{ENV['SUB_USERNAME']}" 
config.registration.password = "#{ENV['SUB_PASSWORD']}" 



On 4 November 2015 at 01:32, Rob Stryker <rstryker at redhat.com> wrote: 
> Hey all: 
> 
> Not sure where else to ask this.  I've been trying to get the SUB_USERNAME 
> and SUB_PASSWORD stuff to work, but it doesn't seem to ;) 
> 
> I've modified my {cdk}/components/rhel/rhel-standalone/Vagrantfile  to 
> include the lines from the README.md, specifically: 
> 
> 
> Vagrant.configure('2') do |config| 
>   # Accepting environment variables 
>     config.registration.subscriber_username = ENV['SUB_USERNAME'] 
>     config.registration.subscriber_password = ENV['SUB_PASSWORD'] 
> 
> When I run vagrant commands, even using CLI (outside eclipse) and pass in my 
> credentials, I still get prompted to register the machine, and it prompts 
> for username/password despite them being passed in via environment 
> variables. 
> 
> I've also double-checked that the process is actually receiving the vars, by 
> running  "strings -a  /proc/22883/environ"  and inspecting the environment. 
> My credentials are properly passed in, and they are correct.  But the 
> vagrant process still prompts me. 
> 
> If I don't pass the credentials in via environment, I get an error seemingly 
> caused by ruby trying to resolve the vars and getting no result... so I know 
> vagrant should be seeing these variables.... but it's still prompting me for 
> credentials. 
> 
> This problem is replicatable even when I change the Vagrantfile to hard-code 
> the credentials rather than referring to SUB_USERNAME / SUB_PASSWORD 
> environment variables. 
> 
> Not only did I try modifying 
> {cdk}/components/rhel/rhel-standalone/Vagrantfile,   I also tried to modify 
> ~/.vagrant.d/Vagrantfile 
> 
> Checking my vagrant-registration plugin, I see 
> vagrant-registration-0.0.8.gem in my {cdk}/plugins folder, and an attempt to 
> re-install the plugin returns "Installed the plugin 'vagrant-registration 
> (0.0.19)'!" but the {cdk}/plugins folder still has the 0.0.8.gem version. 
>

The plugins installed to vagrant end up in a different folder after install. The cdk-1 zip file shipped w/ .8 cdk-2 will (likely) ship with .19


> [rob at rawbdor cdk]$ uname -a 
> Linux rawbdor 4.1.8-100.fc21.x86_64 #1 SMP Tue Sep 22 12:13:06 UTC 2015 
> x86_64 x86_64 x86_64 GNU/Linux 
> 
> 
> Anyone know who I'd ping for more info? 
> 
> - Rob Stryker 
> 
> 
> 
> 
> 
> On 10/28/2015 01:07 PM, Rob Stryker wrote: 
>> 
>> Hey guys: 
>> 
>> I was asked to make a quick-and-dirty demo of what I've got for a CDK 
>> server adapter.   So linking to it here.  It demos creation / start / stop 
>> of one server. A server represents a vagrant file. If the vagrant file 
>> contains multiple vm's, it'll wait for all of them to start. 
>> 
>> It basically functions as a vagrantfile server adapter, and doesn't check 
>> for anything like a .cdk file/folder, since the cdk installation itself 
>> doesn't have such marker files.   I think further discussion will be needed 
>> for how openshift / docker tools should interact with this. 
>> 
>> https://www.dropbox.com/s/hk7ymzf55ttwdmd/cdk_server_adapter.ogv?dl=0 
>> 
>> - Rob Stryker 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/container-tools/attachments/20151104/0aea3028/attachment.htm>