Dev log for upcoming 3.8-13

suman · March 28, 2016, 4:08pm

phillxnet · March 28, 2016, 6:58pm

@suman Tested on a few different systems / configs here and fake serial seems to be functioning as expected.

suman · March 31, 2016, 5:56am

3.8-12.07 is now available!

I made a couple of Rock-on related improvements in this update. Thanks to @pdenhaan for reporting this issue. I’ve also cleared some backlog with Rock-on submissions from @joshi, @bug11 @henfri and @pdenhaan. Great to see these submissions. Please keep them coming! and thank you!

github.com/rockstor/rockstor-core

Catch-22 with failed Rock-ons

opened 10:04AM - 16 Mar 16 UTC

closed 05:11AM - 31 Mar 16 UTC

peterdenhaan

It's possible to end up in nasty catch-22s when rock-ons fail. I was trying to …rig an alternative `btsync-peter` rock-on (the official BTSync is broken at the moment), but made a typo in the port definition. My json file attempted to map port 88888 rather than 8888. Installation obviously fell over because no such port was exposed. So far, so good. When I corrected my json, Rockstor would not refresh because I wasn't allowed to change the port mappings of installed rock-ons and told me to uninstall first. But there was nothing to uninstall. After all, installation had failed. There seems to be no way offered out of this catch-22. I only got myself unstuck by firing up `psql` and deleting all the records for my rock-on from the `storageadmin` tables. The simplest way to fix this would probably be to suppress these port consistency checks when Rock-on installation (as opposed to start-up) has failed. However, there may be more edge cases like this. Given the data duplication between Rockstor's state recorded in `storageadmin` and Docker's own internal state, there is always scope for inconsistencies to arise.

suman · March 31, 2016, 5:56am

glenngould · April 8, 2016, 2:44pm

Hello everybody,

is there any overview regarding new features and improvements for the next version 3.8-13?
Any possible release date which can be shared already?

Sorry for asking, but I was not able to find any related information in the forum so far.

Thanks / regards,
Roland

Flyer · April 8, 2016, 5:28pm

If you want to get an idea follow on github to see what’s going on
Rockstor on GitHub

Flyer

suman · April 8, 2016, 11:01pm

Hi @glenngould, I’d love to bring more predictability with the timing and scope of releases and we are steadily becoming capable of doing so, thanks to support from our subscribers and customers. It will take some more time and $ to reach that point.

Historically speaking, we released a stable update roughly every 4-6 weeks. This release cycle is the slowest till date, but I am planning to close it out within a week. It may be a lighter update in terms of number of issues closed, but there’s enough good/important stuff that doesn’t justify waiting much longer.

That’s the best non-answer answer I can provide Please stay tuned and thanks for your question!

suman · April 9, 2016, 2:43pm

Hello Everyone. 3.8-12.08 is now available!

We’ve closed a few UI related issues that others in our community have kindly reported. Thanks to @ganti_priya and @Flyer for code contributions.

suman · April 9, 2016, 4:22pm

suman · April 11, 2016, 2:46pm

Hi there! 3.8-12.09 is now available. Please test away!

There are two issues fixed in this update. One is a small Rock-on related improvement. The other is an improvement to the way we unmount various resources during pool/share/snapshot deletions.

I’ve been working on adding teaming support(and possibly bonding) which is about 60%, so planning to wrap that up this week. There are a few other important but small(thankfully) issues that are also in the pipeline for this week and hopefully we can all have the stable update towards the end of this week!

github.com/rockstor/rockstor-core

Add Storage only possible when Rock-On not running

opened 01:20PM - 21 Feb 16 UTC

closed 07:50PM - 10 Apr 16 UTC

henfri

enhancement

Hello, currently, RockStor does allow editing and thus adding storage while a r…ock-on is running. But then, when submitting the changes, an error message pops up telling that this action is only possible when the rock-on is not running. This is annoying, as this only comes up, after the user has specified all the settings in good hope that it will run. Proposals: Editing config should only be possible if rockon is off OR Editing config should be possible if rockon is running, but the user should be informed that after the changes a restart is needed. This restart should be offered Greetings, Hendrik

suman · April 11, 2016, 2:46pm

suman · April 13, 2016, 4:07pm

3.8-12.10 is now available!

We’ve closed to issues, thanks for contributions from @Flyer and @ganti_priya! you both rock!
First is a bugfix to sorting behaviour on System → Services page and Second is improvement to handlebar templating in Samba export management.

github.com/rockstor/rockstor-core

Samba share page not displaying correct information for existing shares

opened 08:49AM - 20 Feb 16 UTC

closed 03:22PM - 13 Apr 16 UTC

nicolaslt

bug

Hi, After creating a share, when going back to it via the 'edit' button, some -…if not most- of the inputs do not display the correct data. Example: Read Only always stays on yes. I was on my way to make a pull request for this but it seems to me this page needs more work. I'm happy to do that extra work if we agree it's needed. There are many duplications in the .jst as follow: ``` handlebars {{#if sambaShareIdNotNull}} <input type="text" id="comment" class="form-control" name="comment" value="{{smbShareComment}}" title="Comment string to associate with the new share"> {{else}} <input type="text" id="comment" class="form-control" name="comment" value="Samba-Export" title="Comment string to associate with the new share"> {{/if}} ``` which IMHO should be: ``` handlebars <input type="text" id="comment" class="form-control" name="comment" value="{{smbShareComment}}" title="Comment string to associate with the new share" placeholder="Samba-Export"> ``` And the javascript defines 5 handlebar helpers to render 3 yes/no radio buttons and 2 selects. Couple of bullets for this: - I guess the yes/no radios should be checkboxes - Those helpers defeat the purpose of having a templating engine. Why not use a handlebar partial instead ? Especially as the helpers duplicate the code by quite a bit. Each yes/no helper has 4 lines of html. (1 per permutation between `checked` and the option `name` and `value`) - This is where the original issue comes from; there's a few `this` and scope confusion in the building of the yes/no radios.

suman · April 13, 2016, 4:08pm

suman · April 15, 2016, 3:49pm

Another day, another update… 3.8-12.11 is now available. Please test!

We closed two issues. @Flyer added smtp auth support to our e-mail notification setup as requested by some of you. Second, I fixed a bug in Rock-on profile update. Thanks to @pdenhaan for reporting it and pretty much giving away the fix. We’ve got a great community going, happy friday everybody!

github.com/rockstor/rockstor-core

Update of Rock-on definitions fails when Rock-on in install_failed state

opened 11:26AM - 12 Apr 16 UTC

closed 03:13PM - 15 Apr 16 UTC

peterdenhaan

When a Rock-on installation has failed, the Update button on the UI (`/home#rock…ons`) fails with the following error message: ![image](https://cloud.githubusercontent.com/assets/10416743/14458326/5829b272-00a8-11e6-961e-88c0f8e27257.png) The error is correct: the rock-on's state is `install_failed` rather than `available`. ``` storageadmin=# select * from storageadmin_rockon order by id; id | name | description | version | state | status | link | website | https | icon | ui | volume_add_support | more_info ----+---------------------+------------------------------------------------------------------------+--------------+----------------+-----------------------+------+---------------------------------------------------+-------+-------------------------------------------------------------------------------------------+----+--------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 | BTSync | BitTorrent Sync | 1.0 | install_failed | stopped | | https://www.getsync.com/ | f | | t | t | <h4>Authentication</h4><p>Default username for your BTSync UI is<code>admin</code>and password is<code>password</code></p><h4>Storage</h4><p>You can also assign additional Shares for custom organization of your data.</p> ... ``` But obviously there is nothing that can be uninstalled because BTSync failed to install in the first place. I suspect the update code needs to check for `state != "installed"` rather than `state == "available"`. Manually updating the `storageadmin_rockon` record to `available` state allows the update to proceed successfully. This may be linked with, but not (I think) identical to, #1124.

suman · April 15, 2016, 3:49pm

suman · April 20, 2016, 4:34am

3.8-12.13 is now available!

I merged support for Network Teaming and Bonding that has been under construction for some time. That makes this update into a big one! Thanks to @ganti_priya for UI contributions. I am happy with the design and various teaming profiles and bonding modes are functioning as expected. But I am hoping that everyone in the community that asked for these features will test it thoroughly and report back any issues. In the process of adding Teaming/Bonding support, we’ve also improved how network related dependencies are handled. For example, a nice side effect is that you can now restrict Rockstor management on a designated connection/ip and port.

We also have a new contributor in this update which is always a reason to celebrate. Thanks @ScarabMonkey!

github.com/rockstor/rockstor-core

Support bonded networking

opened 02:18PM - 03 Jan 15 UTC

closed 03:09AM - 20 Apr 16 UTC

schakrava

Major Feature

I tried to set up bonded networking. There were several issues I ran into. ``` …NetworkManager conflicts with Rockstor and they both try to use different interface names and overwrite each others setting. I just uninstalled NetworkManager with yum. Bonded networking adds a file /sys/class/net/bonding_masters which Rockstor tries to enumurate as a network interface and errors out. In system/osi.py network_devices I changed devices = os.listdir('/sys/class/net') to ifpath = '/sys/class/net' devices = [name for name in os.listdir(ifpath) if os.path.isdir(os.path.join(ifpath, name))] so it only enumerates directories. If viewing the interface properties in Rockstor, even if no changes are made and cancel is clicked, Rockstor rewrites the ifcfg file and clobbers the bonding settings ``` It would be great if Rockstor could fully support bonded networking for either failover or aggregation, but at minimum it should play nicely with a manual setup.

suman · April 20, 2016, 4:34am