I would recommend that Shane work on this. The reason cdmi can contact production is because it is talking to the database directly, not the api which the kbase.us name resolves to. I'm of the opinion that the test environment should be self contained, and developers should identify the necessary datasets that need to be in the test environment for their code to pass testing there. To move forward on the cbd service we should identify the necessary datasets, and load them into the test shock instance. Not the local cbd instance, but the shock VM in the test environment. ----- Original Message -----
From: "Thomas Brettin" <[email protected]> To: "Dan Olson" <[email protected]>, [email protected] Cc: [email protected] Sent: Wednesday, September 25, 2013 10:12:34 AM Subject: Re: [Release-team] release process stuck on cbd
The curl on the test head node doesn't work.
I can't get to the bcd test host cause it's not in the etc/hosts file.
Dan, please assign a sysadmin assigned to this module so we can get it done today and let me know who that is.
We should not take the position that the cbd module can not contact the production shock service for read only access.
brettin@t13:/$ source /kb/deployment/user-env.sh brettin@t13:/$ all_entities_Genome | wc 6321 6321 63505
t1:~> curl http://140.221.43.50/services/shock-api
<html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.0.5</center> </body> </html>
On Sep 25, 2013, at 10:04 AM, Dan Olson <[email protected]> wrote:
I'm not sure, you could try entering the ip address for production 140.221.43.50 into the deployment configuration.
----- Original Message -----
From: "Thomas Brettin" <[email protected]> To: "Dan Olson" <[email protected]> Cc: [email protected] Sent: Wednesday, September 25, 2013 10:01:56 AM Subject: Re: [Release-team] release process stuck on cbd
can we give them an IP address?
On Sep 25, 2013, at 10:01 AM, Dan Olson <[email protected]> wrote:
kbase.us doesn't make it out of the test environment. It is redirected based on the host name. There is no easy way around this.
If they have data that is necessary to build in the production shock - they will need to load this data into the test shock.
----- Original Message -----
From: "Thomas Brettin" <[email protected]> To: [email protected] Sent: Wednesday, September 25, 2013 9:55:16 AM Subject: [Release-team] release process stuck on cbd
This is in the deploy team hands. It appears that a connection to kbase.us/services/shock-api/node is failing because.
Network controls needs to be investigated.
Can we get this one unstuck?
Thanks, Tom _______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team