Carlos, I found what was wrong with my configuration; onedatastore show default reveals that BASE_PATH was pointing at the wrong path. (This is because I started with one path and then later renamed the directory.)
onedatastore update default did not let me change this BASE_PATH, so I had to modify the DB content directly, mysql> update datastore_pool set body="<DATASTORE> … </DATASTORE>" where oid=1; and also had to restart oned in order to flush the memory contents. After this, onedatastore list now shows -bash-4.1$ od list ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM 0 system - - - 0 sys - ssh 1 default 434.9G 91% production 0 img fs ssh 2 files 0M - - 0 fil fs ssh Thanks again, HyunWoo From: Hyunwoo Kim <hyun...@fnal.gov<mailto:hyun...@fnal.gov>> Date: Tuesday, December 3, 2013 9:15 AM To: Hyunwoo Kim <hyun...@fnal.gov<mailto:hyun...@fnal.gov>>, Carlos Martín Sánchez <cmar...@opennebula.org<mailto:cmar...@opennebula.org>> Cc: "users@lists.opennebula.org<mailto:users@lists.opennebula.org>" <users@lists.opennebula.org<mailto:users@lists.opennebula.org>> Subject: Re: [one-users] oneimage create command in ON3.4 and up Carlos, in your email, you said, "The datastore size is initialized to 0, and then populated with the right size" What do you mean by "right size" here? How do we set the right size in the first place? Thanks, HyunWoo FermiCloud From: Hyunwoo Kim <hyun...@fnal.gov<mailto:hyun...@fnal.gov>> Date: Tuesday, December 3, 2013 8:59 AM To: Carlos Martín Sánchez <cmar...@opennebula.org<mailto:cmar...@opennebula.org>> Cc: "users@lists.opennebula.org<mailto:users@lists.opennebula.org>" <users@lists.opennebula.org<mailto:users@lists.opennebula.org>> Subject: Re: [one-users] oneimage create command in ON3.4 and up Hi, Thanks for the reply. My oned.log has those messages Tue Dec 3 08:53:08 2013 [InM][I]: Monitoring datastore default (1) Tue Dec 3 08:53:08 2013 [ImM][I]: Datastore default (1) successfully monitored. but I still can not do oneimage create with the same error message; -bash-4.1$ oneimage create firstimage.template --datastore default Not enough space in datastore Any other suggestion? Thank you. HyunWoo FermiCloud From: Carlos Martín Sánchez <cmar...@opennebula.org<mailto:cmar...@opennebula.org>> Date: Tuesday, December 3, 2013 4:06 AM To: Hyunwoo Kim <hyun...@fnal.gov<mailto:hyun...@fnal.gov>> Cc: "users@lists.opennebula.org<mailto:users@lists.opennebula.org>" <users@lists.opennebula.org<mailto:users@lists.opennebula.org>> Subject: Re: [one-users] oneimage create command in ON3.4 and up Hi, The datastore size is initialized to 0, and then populated with the right size after the monitorization begins to work. Maybe there was a problem trying to monitor it. Take a look at /var/log/one/oned.log, you should have messages like these: Fri Nov 29 17:29:19 2013 [InM][D]: Monitoring datastore default (1) Fri Nov 29 17:29:20 2013 [ImM][D]: Datastore default (1) successfully monitored. Or an error message from the drivers. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org<http://www.OpenNebula.org> | cmar...@opennebula.org<mailto:cmar...@opennebula.org> | @OpenNebula<http://twitter.com/opennebula><mailto:cmar...@opennebula.org> On Mon, Dec 2, 2013 at 11:37 PM, Hyun Woo Kim <hyun...@fnal.gov<mailto:hyun...@fnal.gov>> wrote: Hi, Let me ask a basic question. I just started testing ON4.2 and when I use oneimage command to register a first image, I am getting the following error message -bash-4.1$ oneimage create firstimage.template --datastore default Not enough space in datastore I guess this is because the "default" datastore has "0M" size as shown below, -bash-4.1$ onedatastore list ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM 0 system - - - 0 sys - ssh 1 default 0M - production 0 img fs ssh My question is, how can I increase this size? I could not find relevant information from onedatastore help, I guessed this size will increase when I add a new host, create a cluster, add the host in this cluster and create a new virtual network and add it to the cluster etc, but I am still getting the same error message.. Thanks in advance. HyunWoo KIM FermiCloud _______________________________________________ Users mailing list Users@lists.opennebula.org<mailto:Users@lists.opennebula.org> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
