Bug #4130

cannot use files datastore if BRIDGE_LIST is set and frontend doesn't see those files

Added by Rolandas Naujikas almost 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:11/03/2015
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Drivers - Storage
Target version:Release 4.14.2
Resolution:worksforme Pull request:
Affected Versions:OpenNebula 4.12, OpenNebula 4.14

Description

When opennebula frontend don't share files with images/files datastores, then we have BRIDGE_LIST as list of some nodes with access to those images/files.
For the moment opennebula tm/*/context scripts are not corrected to support BRIDGE_LIST and copy from remote file system with ssh as in other actions.

As a workaround we are using some directory on frontend to put those files and register them with image template using SOURCE attribute.

History

#1 Updated by Ruben S. Montero almost 5 years ago

  • Target version set to Release 4.14.2

#2 Updated by Javi Fontan almost 5 years ago

  • Assignee set to Javi Fontan

#3 Updated by Javi Fontan almost 5 years ago

  • Status changed from Pending to Closed
  • Resolution set to worksforme

The files datastore is meant to be visible in the frontend where the iso images are created. We don't think this will be changed in the short term as it is only used on VM start. It also needs to be visible in the frontend to add scripts to it using the CLI or Sunstone.

If there is a compelling reason to make the context image in other node please add a comment and we will reopen the issue.

#4 Updated by Rolandas Naujikas almost 5 years ago

Agree on that. Also context scripts are always run on frontend.
We need describe in the documentation or in known problems list
to don't put BRIDGE_LIST into files datastore configuration
or make it available in the frontend.

Also available in: Atom PDF