Skip to main content

the avatar of Mauro Parra-Miranda

Mobile SDK 1.8.0.1RC1 (re post)


Hi Titans,

As most of you are aware, the release candidates for both products were initially dropped last week:

Mobile 1.8:

Studio 1.0.7:

We're hoping to go out with GA releases next week, and are currently looking to address any show-stopping issues before that release is final.  To that end, we appreciate your help in installing these latest release candidates, and reporting any issues you may find with them.  To report a bug, please use our community JIRA project, as usual, making sure to provide a small, but complete test case (an app.js and/or the smallest possible set of files necessary to recreate the issue) and conform as much as possible to the JIRA checklist below:


In the Comments section, please make a note that you used the 1.8.0.1 Release Candidate when reporting the bug.  Again, test cases are critical, as they will allow us to quickly home in on the problem.

Thanks for your help, and for letting us help you get your app up and running on 1.8!

the avatar of Mauro Parra-Miranda

Twine

Cuando pense que no me podría sorprender más, el MIT lo logra de nuevo. Tienen que conocer Twine. Básicamente, podrán twittear en el momento que alguno de los sensores detecte movimiento, humedad, presencia de objetos metalicos a la redonda, etc. 

Simplemente increible. Podría twittear cuando el piso debajo de tu platon falso tenga humedad. Muy útil para un Datacenter, por ejemplo. O cuando comience a ser muy caliente. 

Las posiblidades son infinitas. 
the avatar of Mauro Parra-Miranda

the avatar of Han Wen Kam

My openSUSE 12 Journal - 5: Desktop Bits & Bytes

This is week 3 of using 12.1 and still lovin' it.  This journal entry covers a few disparate topics, from wifi to graphics cards, as I go about my daily routine in the office (stuff I actually get paid doing) with openSUSE 12.1 on my Lenovo Thinkpad.


Can't locate your hidden Wifi access point?
Here is a neat command (as root) that you can execute to help NetworkManager connect to a hidden wireless access point OR when NetworkManager is unable to detect your desired wireless point fast enough in a wifi-saturated environment.

iwlist wlan0 scanning essid MyWifi

where wlan0 is usually your default wifi device, if you are unsure, execute ip add to verify.
MyWifi is the name of your desired/hidden wireless access point.  For ease of use, you could wrap this into a nice little script.
Read more »
the avatar of Will Stephenson

a silhouette of a person's head and shoulders, used as a default avatar

XDC 2012: Nuremberg!

Yes! The board has decided! XDC comes to Nuremberg!

For 2012 we (Egbert Eich, Professor Hopf, and I) will be hosting the annual X conference in Nuremberg!

Egbert will try to get the main SuSE conference room, or, failing that, Matthias will try to get us a university aula, so the venue itself will work itself out beautifully in one way or another. Then... Nuremberg is one of those places which is perfect for large crowds who need food and some liquids in the evening (frankonian/bavarian beergarten culture), so it is the perfect (and highly affordable) conference area from that point of view. And, the best part, even though Nuremberg is not the international hub that Frankfurt is, or the european hub that Munich is, it is halfway between the two, and travel is relatively easy from either of those points, either you take the plane, or you take a much more comfortable train from either airport, and get to Nuremberg in pretty much the same time. You can really make a big save comparing those two airports when flying inside european aerospace, and this for no time difference. One insider tip though: you get to ride the ICE at full speed (300+km/h!) when traveling from Munich (you do have to endure the rather pedestrian S-bahn for 45 minutes though).

Anyway, the main action item now is that Egbert can start to poke SuSE to see when their main conference room is available for 3 days in september 2012 (working network and enough power sockets are a given then!). I doubt that we will get an answer still in the three remaining weeks of this year.

The actual proposal e-mail sent to the board is sadly only available to X.org foundation members, but a wiki page will soon be created which recreates most of that information. But rest assured, we will get close to the wonderful experiences of XDC Toulouse (thank you Matthieu!) and XDC chicago (thank you Michael!) indeed!

(oh, and btw, we have a FOSDEM DevRoom this year, which is rapidly getting its schedule filled! If you are coming, get your talk in right now: first come, first serve!)

a silhouette of a person's head and shoulders, used as a default avatar

The Exo Typeface Family

Some week ago, I’ve stumbled upon a very promising font project. It’s called the Exo Typeface Family and I think this could be a valuable addition to our distribution:

The sans serif font is beautifully crafted and contains 9(!) different width as you can see in the following graphic:

Natanael, the graphic designer, wrote about his font:

Today Exo is already a very mature font family, with over 700 characters supporting most Western, Central and Eastern European languages – and it can still go further! This coverage has been reached for all 9 weights, the maximum possible on the web. Each weight has an upright style and the corresponding ‘true’ italic style. Many ‘techno’ fonts have only the simple slanted oblique companion styles, but for the highest typographic quality it is essential to have true italics that are drawn specially.

Some unique OpenType features:

If this project reaches its funding goal it will be published in Google Web Fonts under the SIL Open Font License. Currently, almost 80% is pledged, but only 18 days are left. If you find this project useful, please help Natanael and make the Web a more beautiful place. I already did so. Thanks!

a silhouette of a person's head and shoulders, used as a default avatar

Cooking with DocBook

Hi DocBook lovers,

browsed through a book, used your favorite search engine, or posted on LinkedIn, Xing, or the DocBook mailinglist to hunt for answers to your problems?

As an additional alternative, I’m happy to announce my latest project:

The DoCookBook Project
(released  under Creative Commons License)

The tongue-twisting name is a word play and picks up the two central topic about DocBook and cookbook.

What is the “DoCookBook Project”?

This project is a collection of problems and solution towards DocBook and the DocBook stylesheets. The book contains helpful topics with step-by-step instructions.

Why another project about DocBook?

Information about DocBook can be find in books or somewhere in the Internet. However, it can be an exhausting task to extract the necessary piece which fits to your problem. This project can help you to get your work done more quickly.

Is it done?

Not yet. Currently it is a draft. However, the structure is almost complete. The book contains some useful topics and it will be improved and extended over time.

Can I see the source code?

Sure! The source code of this book is published and maintained as a Mercurial repository.

Ok, you’ll get me! How can I support the project?

  • Register on the project mailinglist to influence the direction or to get updates
  • Point out typos, ambiguities, inconsistencies, or errors.
  • Let me know what’s your favorite topic.
    Send me your topics directly or use the project’s ticket system (see Ticket#15).
    If you want to use the latter, you’ll have to register at Sourceforge
  • Write your own topics.
  • Create a cool new layout.
  • Support this project and donate a small amount.

Have fun!

the avatar of Alex Eftimie

AppStream Software Center on Fedora

Watching software-center code changes, this one came into my attention: an effort from Giovanni Campagna into bringing Software Center to Fedora, using the PackageKit backend I’ve been working on this summer.

It’s nice to see someone showing interest, and also picking up the code :) .

I must definitely get the time to fix my experimental OBS build, and see the openSUSE version running again. For the record, there is room for improvement on the performance part (especially starting up speed).

a silhouette of a person's head and shoulders, used as a default avatar

Xen or KVM

Since little more than half a year, I am in the process of installing a new virtualization Platform. One of the hardest decisions to make was if we should use Xen or go with KVM. We already have Xen in production and I know that it works well. From KVM we expect, that it will be growing faster then Xen and be the right thing on the long run.

The machines that I have as hosts are quite powerful. They are 48 Core AMD Opteron with 256 GByte of memory, and FCoE based Storage devices for the guests. We are using a converged network where both, FC and Ethernet, go over the same redundant 10GBit ethernet line. Storage is external FC storage from different devices.

The most important features that we need for such a platform are these:

  • Stability
  • Performance
  • Tools

After doing a number of tests, it is obvious that both systems are stable. I did not encounter crashes related to the hypervisor technology.

Performance is also an interesting point. Especially the speed of block and network devices is not the best when using virtualized guests. This holds true for both, KVM and Xen. Note, that comparing CPU or Memory performance in standard environments is not very useful. Even if one of the systems performs slightly better, both are very close to hardware speed in terms of CPU and Memory. However outbound connectivity is an issue for both.

One exception is when you invest some more effort and use the new NUMA features provided with the latest Xen. The IO performance of network devices was roughly 4 times the performance without using NUMA.

One of the drawbacks when using NUMA on Xen is, that you have to use the tool “xl” instead of “xm”. For some unknown reason, you can dump configurations from “xl” only in SXP format, but “xl” won’t let you start a guest from such a configuration. This renders the tool quite useless in a production environment.

This brings me to Tools. For me, Xen has the tools that are easier to operate than KVM. Especially life migration syntax is way easier on Xen. On the other hand, both are simple enough to be operated by experienced people. For those that do not like the command line, “libvirt” offers a number of graphical tools that can cope with both, Xen and KVM.

One thing to mention is, that with Xen you can enable a locking mechanism that prevents you from running the same guest on different Hosts. I have yet to find similar functionality on KVM.

Now let me add some words about issues I encountered. As I already told, we have Xen running productive and it works quite well. I also found the Xen developers being relatively responsive when some bug occurs. From my other blog entries you can see, that Xen also offers a number of debugging capabilities.

With KVM, there are two major issues I have right now

  • Life migrations are not safe in KVM. I repeatedly encountered block device corruptions when doing life migrations. This also holds true when using “cache=none” for the qemu configuration. Simple migrations still work without problems.
  • The networking inside a 10GBit environment behaves strangely. When connecting a Guest to a remote server I get connection speeds at about 30-40kByte/s. All the connections between the respective hobs in this environment work as expected (Guest -> Host, Host -> Server).

Resume:

Both, KVM and Xen are usable if you do not need life migrations. OTOH life migration is an essential feature in a production environment. It enables you to service a Host without taking down the guests. If the life migration feature is not fixed until SLES11-SP2, I will have to return to Xen.

For the moment, KVM is not on par with Xen. However, in the long run I expect that KVM will gain momentum and eventually be the platform of choice. If I had to select a platform in a critical business environment today, I would go with Xen. On the long run, it might be better to go with KVM, but this depends on the further development of KVM.

The major development areas that will influence my decisions in future will be

  • IO Speed
  • Support of NUMA architectures
  • Support for HA features like “Remus” or “Kemari”

The race is still open…