[
https://issues.apache.org/jira/browse/VCL-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303636#comment-14303636
]
ASF subversion and git services commented on VCL-767:
-----------------------------------------------------
Commit 1656840 from [~arkurth] in branch 'vcl/trunk'
[ https://svn.apache.org/r1656840 ]
VCL-16
Added utils.pm::get_reservation_management_node_hostname. This is used to
display more useful information when a cluster request fails.
Changed utils.pm::set_reservation_lastcheck to allow multiple reservation IDs
to be passed. Updated call in VIM_SSH.pm.
Updated utils.pm::reservation_being_processed to also retrieve the parent
reservation ID from the database for cluster requests. Duplicate processes were
being forked if a child reservation already ran before the parent finished.
Removed call to update_request_state in State.pm::reservation_failed. This gets
handled by state_exit. It was not checking if the reservation was the parent.
Updated State.pm::wait_for_all_reservations_to_begin to display information
about which management nodes the reservations belong to.
Updated State.pm::wait_for_child_reservations_to_exit to check for both a
computerloadlog 'begin' and 'exited' entry for each reservation. It was only
checking for 'exited'. As a result, the loop ran until it timed out if any
child reservation process had never started and added a 'begin' entry.
VCL-767
Updated utils.pm::determine_remote_connection_target to check the argument for
a '@' sign. run_scp_command is passing [email protected]. This was failing. If it
detects this, the 'user@' is removed from the argument.
> Allow dynamic private IP addresses, remove /etc/hosts requirement
> -----------------------------------------------------------------
>
> Key: VCL-767
> URL: https://issues.apache.org/jira/browse/VCL-767
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Affects Versions: 2.3.2
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.4
>
>
> Some provisioning modules require dynamic private IP addressing. VCL doesn't
> currently support this.
> To summarize the situation and changes, the backend code currently reads
> /etc/hosts in order to determine the private IP address of a node. It does
> not rely on the computer.privateIPaddress field in the database. Several
> node configuration tasks depend on knowing the correct private IP address.
> The backend code also currently uses the computer.hostname value to SSH into
> nodes. As a result, it depends on hostname-private IP address resolution
> working correctly -- which is usually accomplished via /etc/hosts.
> I will change the code to:
> (1) Not read or reference /etc/hosts at all
> (2) Use the computer.privateIPaddress field as the authoritative value
> (3) Use the private IP address instead of the hostname for all SSH and other
> connections
> (4) Add utils.pm::update_private_ip_address
> This will allow any provisioning module to have control over how private IP
> addresses are allocated. If they are dynamically allocated when a node is
> loaded or instantiated, the provisioning module can retrieve the dynamic
> private IP address from Openstack or some other provisioning API, and call
> update_private_ip_address to set the correct value in the database. The
> provisioning module should also call $self->data->set_private_ip_address.
> When control is passed from the provisioning to the OS module, everything
> should be set up correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
