Canonical Voices

Posts tagged with 'uncategorized'

Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140325 Meeting Agenda


ARM Status

nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    4 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   ogasawara    core-1311-kernel    1 work item   
      core-1403-hwe-stack-eol-notifications    2 work items   
   smb    servercloud-1311-openstack-virt    3 work items   


Status: Trusty Development Kernel

The 3.13.0-19.40 Trusty kernel has been uploaded to the archive. We’ll
anticipate one more upload before kernel freeze on Thurs Apr 3. If
there are any patches which need to land in our 14.04 Trusty kernel, get
them submitted to the Ubuntu kernel team mailing list asap. After
kernel freeze, all patches are subject to our Ubuntu SRU policy.
—–
Important upcoming dates:
Thurs Apr 03 – Kernel Freeze (~1 week away)
Thurs Apr 17 – Ubuntu 14.04 Final Release (~3 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Mar. 25):

  • Lucid – No changes this cycle
  • Precise – No changes this cycle
  • Quantal – Testing
  • Saucy – Testing

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140318 Meeting Agenda


ARM Status

nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    4 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   ogasawara    core-1311-kernel    1 work item   
      core-1403-hwe-stack-eol-notifications    2 work items   
   smb    servercloud-1311-openstack-virt    3 work items   
      servercloud-1311-openstack    1 work item   


Status: Trusty Development Kernel

The 3.13.0-18.38 Trusty kernel has been uploaded to the archive. This
is based on the v3.13.6 upstream stable kernel. I would also like to
remind everyone that Trusty Kernel Freeze is fast approaching on Thurs,
Apr 3. Please make sure to get any outstanding patches submitted to our
Ubuntu kernel team mailing list for review asap. After kernel freeze,
all patches are subject to our Ubuntu SRU policy.
—–
Important upcoming dates:
Thurs Mar 27 – Final Beta (~1 week away)
Thurs Apr 03 – Kernel Freeze (~2 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – No changes this cycle
  • Precise – No changes this cycle
  • Quantal – Verification
  • Saucy – Verification

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussion.

Read more
Pat Gaughen

The Server team just finished up the second day of the Ubuntu Developer Summit (UDS) March 2014 (see http://summit.ubuntu.com/uds-1403/track/servercloud/ for the Server track). I may be biased (well, actually, I know I am), but I think its been very interesting – lots of good, thoughtful discussions around where we are and where we’re heading. Check out the videos and let us know what you think.

One video from today’s UDS sessions, I wanted to specifically highlight is the demo Robie Basak gave on uvtool.  Uvtool is, as Robie explains in the video, a very simple tool for setting up kvm guests – he calls it the glue that brings together several existing tools.  Just go watch it – http://www.youtube.com/embed/Ue0C2ssp450 and then go try it.

In December, Serge did a writeup on uvtool, I think that’s worth a read also – http://s3hh.wordpress.com/2013/12/12/quickly-run-ubuntu-cloud-images-locally-using-uvtool/

Anyhow, time to prepare for the last day of UDS. Enjoy!

Read more
David Henningsson

Headsets come in many sorts and shapes. And laptops come with different sorts of headset jacks – there is the classic variant of one 3.5 mm headphone jack and one 3.5 mm mic jack, and the newer (common on smartphones) 3.5 mm headset jack which can do both. USB and Bluetooth headsets are also quite common, but that’s outside the scope for this article, which is about different types of 3.5 mm (1/8 inch) jacks and how we support them in Ubuntu 14.04.

You’d think this would be simple to support, and for the classic (and still common) version of having one headphone jack and one mic jack that’s mostly true, but newer hardware come in several variants.

If we talk about the typical TRRS headset – for the headset itself there are two competing standards, CTIA and OMTP. CTIA is the more common variant, at least in the US and Europe, but it means that we have laptop jacks supporting only one of the variants, or both by autodetecting which sort has been plugged in.

Speaking of autodetection, hardware differs there as well. Some computers can autodetect whether a headphone or a headset has been plugged in, whereas others can not. Some computers also have a “mic in” mode, so they would have only one jack, but you can manually retask it to be a microphone input.
Finally, a few netbooks have one 3.5 mm TRS jack where you can plug in either a headphone or a mic but not a headset.

So, how would you know which sort of headset jack(s) you have on your device? Well, I found the most reliable source is to actually look at the small icon present next to the jack. Does it look like a headphone (without mic), headset (with mic) or a microphone? If there are two icons separated by a slash “/”, it means “either or”.

For the jacks where the hardware cannot autodetect what has been plugged in, the user needs to do this manually. In Ubuntu 14.04, we now have a dialog:
What-did-you-plug-in
In previous versions of Ubuntu, you would have to go to the sound settings dialog and make sure the correct input and output were selected. So still solvable, just a few more clicks. (The dialog might also be present in some Ubuntu preinstalls running Ubuntu 12.04.)

So in userspace, we should be all set. Now let’s talk about kernels and individual devices.

Quite common with Dell machines manufactured in the last year or so, is the version where the hardware can’t distinguish between headphones and headsets. These machines need to be quirked in the kernel, which means that for every new model, somebody has to insert a row in a table inside the kernel. Without that quirk, the jack will work, but with headphones only.
So if your Dell machine is one of these and not currently supporting headset microphones in Ubuntu 14.04, here’s what you can do:

  • Check which codec you have: We currently can enable this for ALC255, ALC283, ALC292 and ALC668. “grep -r Realtek /proc/asound/card*” would be the quickest way to figure this out.
  • Try it for yourself: edit /etc/modprobe.d/alsa-base.conf and add the line “options snd-hda-intel model=dell-headset-multi”. (A few instead need “options snd-hda-intel model=dell-headset-dock”, but it’s not that common.) Reboot your computer and test.
  • Regardless of whether you manage to resolve this or not, feel free to file a bug using the “ubuntu-bug audio” command. Please remove the workaround from the previous step (and reboot) before filing the bug. This might help others with the same hardware, as well as helping us upstreaming your fix to future kernels in case the workaround was successful. Please keep separate machines in separate bugs as it helps us track when a specific hardware is fixed.

Notes for people not running Ubuntu

  • Kernel support for most newer devices appeared in 3.10. Additional quirks have been added to even newer kernels, but most of them are with CC to stable, so will hopefully appear in 3.10 as well.
  • PulseAudio support is present in 4.0 and newer.
  • The “what did you plug in”-dialog is a part of unity-settings-daemon. The code is free software and available here.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140304 Meeting Agenda


ARM Status

nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

sorry

   apw    core-1311-kernel    4 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   ogasawara    core-1311-kernel    1 work item   
   smb    servercloud-1311-openstack-virt    4 work items   


Status: Trusty Development Kernel

The 3.13.0-15.35 Trusty kernel is available in the archive. This is
bssed on the v3.13.5 upstream stable update. Our unstable branch has
also been rebased to track the latest v3.14-rc5 release.
—–
Important upcoming dates:
Thurs Mar 27 – Final Beta (~3 weeks away)
Thurs Apr 03 – Kernel Freeze (~4 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Testing
  • Precise – Testing
  • Quantal – Testing
  • Saucy – Testing

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140225 Meeting Agenda


ARM Status

T/master: support for the Beaglebone/Beaglebone black boards was added to the
armhf generic multiplatform kernel


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:


Milestone Targeted Work Items

   apw    core-1311-kernel    4 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   ogasawara    core-1311-kernel    1 work item   
   smb    servercloud-1311-openstack-virt    4 work items   


Status: Trusty Development Kernel

The 3.13.0-12.32 Trusty kernel is available in the archive. It’s pulled
the v3.13.4 upstream stable updates. We have also queued the next
v3.13.5 upstream stable patches and anticipate this to be uploaded
shortly. Our unstable branch has also been rebased to track the latest
v3.14-rc4 release.
—–
Important upcoming dates:
Thurs Feb 27 – Beta 1 (~2 days away)
Thurs Mar 27 – Final Beta (~4 weeks away)
Thurs Apr 03 – Kernel Freeze (~5 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Verification and Testing
  • Precise – Verification and Testing
  • Quantal – Verification and Testing
  • Saucy – Verification and Testing

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140218 Meeting Agenda


ARM Status

Nothing new to report this week.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:


Milestone Targeted Work Items

   apw    core-1311-kernel    4 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   ogasawara    core-1311-kernel    1 work item   
   smb    servercloud-1311-openstack-virt    6 work items   


Status: Raring Development Kernel

We have packaged our 3.13.0-9.29 Trusty kernel and uploaded to our
canonical-kernel-team ppa. This primarily pulls in the latest v3.13.3
upstream stable updates. We have also started tracking the v3.14 kernel
and have recently rebased our unstable branch to v3.14-rc3.
—–
Important upcoming dates:
Thurs Feb 20 – Feature Freeze (~2 dayss away)
Thurs Feb 27 – Beta 1 (~1 week away)
Thurs Mar 27 – Final Beta (~5 weeks away)
Thurs Apr 03 – Kernel Freeze (~6 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Prep’ing kernels
  • Precise – Prep’ing kernels
  • Quantal – Prep’ing kernels
  • Saucy – Prep’ing kernels

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140211 Meeting Agenda


ARM Status

Nothing new to report.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   ogasawara    core-1311-kernel    3 work items   
      client-1311-xorg-general    1 work item   
   smb    servercloud-1311-openstack-virt    6 work items   


Status: Trusty Development Kernel

We have uploaded the 3.13.0-8.27 Trusty kernel to the archive which pulled in the latest v3.13.2 upstream stable updates.
We are also starting to work on opening up our first v3.14 rebase which will be available from our ubuntu-trusty unstable branch.
I want to also point out that the proposal for a 12.04.5 point release appears to have widespread support. This 5th point release for Precise will provide the linux-lts-trusty kernel in 12.04.
—–
Important upcoming dates:
Thurs Feb 20 – Feature Freeze (~1 weeks away)
Thurs Feb 27 – Beta 1 (~2 weeks away)
Thurs Mar 27 – Final Beta (~6 weeks away)
Thurs Apr 03 – Kernel Freeze (~7 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Testing
  • Precise – Testing
  • Quantal – Testing
  • Saucy – Testing

    We are in a holding pattern waiting to see if any regressions show up that would cause us
    to respin before the 12.04.4 release goes out.

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140204 Meeting Agenda


ARM Status

nothing new to report this week.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   ogasawara    core-1311-kernel    3 work items   
      client-1311-xorg-general    1 work item   
   smb    servercloud-1311-openstack-virt    6 work items   


Status: Trusty Development Kernel

We have uploaded a new 3.13.0-7.25 Trusty kernel to the archive. This
includes a rebase to the first v3.13.1 upstream stable release. We have
also merged the powerpc and lowlatency flavors back into our main repo.
I would also like to note that the 12.04.4 release comes out this Thurs.
This will officially introduce the Saucy hardware enablement kernel back
into Precise.
—–
Important upcoming dates:
Thurs Feb 20 – Feature Freeze (~2 weeks away)
Thurs Feb 27 – Beta 1 (~3 weeks away)
Thurs Mar 27 – Final Beta (~7 weeks away)
Thurs Apr 03 – Kernel Freeze (~8 weeks away)
Thurs Feb 6 – 12.04.4 Final Release (~2 days away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Testing
  • Precise – Testing
  • Quantal – Testing
  • Saucy – Testing

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Michael Hall

As I mentioned in my last post, I’m with the rest of my team in Orlando this week for a sprint. We are joined by many other groups from Canonical, and unfortunately we didn’t have enough meeting rooms for all of the breakout session, so the Community team was forced (forced I tell you) to meet on the patio by the pool.

We have had a lot of good discussions already, and we have four days left.  You’ll start to seem some of the new ideas and changes going into effect next week.  Until then, stay tuned.

Read more
Michael Hall

Last week I posted on G+ about the a couple of new sets of QML API docs that were published.  Well that was only a part of the actual story of what’s been going on with the Ubuntu API website lately.

Over the last month I’ve been working on implementing and deploying a RESTful JSON service on top of the Ubuntu API website, and last week is when all of that work finally found it’s way into production.  That means we now have a public, open API for accessing all of the information available on the API website itself!  This opens up many interesting opportunities for integration and mashups, from integration with QtCreator in the Ubuntu SDK, to mobile reference apps to run on the Ubuntu phone, or anything else your imagination can come up with.

But what does this have to do with the new published docs?  Well the RESTful service also gives us the ability to push documentation up to the production server, which is how those docs got there.  I’ve been converting the old Django manage.py scripts that would import docs directly into the database, to instead push them to the website via the new service, and the QtMultimedia and QtFeedback API docs were the first ones to use it.

Best of all, the scripts are all automated, which means we can start integrating them with the continuous integration infrastructure that the rest of Ubuntu Engineering has been building around our projects.  So in the near future, whenever there is a new daily build of the Ubuntu SDK, it will also push the new documentation up, so we will have both the stable release documentation as well as the daily development release documentation available online.

I don’t have any docs yet on how to use the new service, but you can go to http://developer.ubuntu.com/api/service/ to see what URLs are available for the different data types.  You can also append ?<field>=<value> keyword filters to your URL to narrow the results.  For example, if you wanted all of the Elements in the Ubuntu.Components namespace, you can use http://developer.ubuntu.com/api/service/elements/?namespace__name=Ubuntu.Components to do that.

That’s it for today, the first day of my UbBloPoMo posts.  The rest of this week I will be driving to and fro for a work sprint with the rest of my team, the Ubuntu SDK team, and many others involved in building the phone and app developer pieces for Ubuntu.  So the rest of this week’s post may be much shorter.  We’ll see.

Happy Hacking.

Read more
Michael Hall

So it’s not February first yet, but what the heck I’ll go ahead and get started early.  I tried to do the whole NaBloPoMo thing a year or so ago, but didn’t make it more than a week.  I hope to do better this time, and with that in mind I’ve decided to put together some kind of a plan.

First things first, I’m going to cheat and only plan on having a post published ever week day of the month, since it seems that’s when most people are reading my blog (and/or Planet Ubuntu) anyway, and it means I don’t have to worry about it over the weekends.  If you really, really want to read a new post from me on Saturday……you should get a hobby.  Then blog about it, on Planet Ubuntu.

To try and keep me from forgetting to blog during the days I am committing to, I’ve scheduled a recurring 30 minute slot on my calendar.  UbBloPoMo posts should be something you can write up in 30 minutes or less, I think, so that should suffice.  I’ve also scheduled it for the end of my work day, so I can talk about things that are still fresh in my mind, to make it even easier.

Finally, because Europe is off work by the end of my day, I’m going to schedule all of my posts to publish the following morning at 9am UTC (posts written Friday will publish on Monday morning).  I’ve been doing this for a while with my previous posts, and it seems to get more views when I do. For example, this post was written yesterday, but posted while I was still sound asleep this morning.  The internet is a magical place.

So, today being Friday, I will be writing my first actual UbBloPoMo entry this evening, and it will post on Monday February 3rd.  What will it be about I wonder?  The suspense is killing me.

 

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140121 Meeting Agenda


ARM Status

Nothing new to report this week.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

No new update this week.


Status: Trusty Development Kernel

No new update this week.


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Holding
  • Precise – Holding
  • Quantal – Holding
  • Saucy – Holding

    We are in a holding pattern waiting to see if any regressions show up that would cause us
    to respin before the 12.04.4 release goes out.

    Current opened tracking bugs details:

  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html

    Note: Raring hit EOL and is no longer supported. However, the lts-backport-raring kernel
    *WILL* continue to be supported until the first point release of the next LTS (14.04.1).


Open Discussion or Questions? Raise your hand to be recognized

No meeting next week due to the kernel team sprint.
The next meeting is scheduled for February 4th, 2014.

Read more
Shuduo

  1. start from official tutorial http://developer.ubuntu.com/scopes/tutorial/

    1. implement search function

    2. implement preview function

    3. modify data/XXXX.scope

    4. modify data/unity-scope-XXXX.service.in

    5. modify XXXX.pro

    6. build executable file, and dbus service file out

    7. install executable file, scope file and service file.

    8. killall unity-scope-home to restart the Home scope so that it loads the new scope

  2. what’s scope? what’s master scope?

    1. Scope

The search engine itself, talking to a web service or a local database. It can be exposed to the user in two ways in the Dash: as a standalone scope or as part of a master scope.

  1. Master scope

The architecture used to merge multiple scopes in the same Dash view.

  1. how to debug?

    1. use libunity-tool -g

  2. My first scope project

    1. lp:~sangshuduo/+junk/scope500px

 

  1. BKMs and tips

    1. recommend C language to programming scope for performance although python and vala still working

      1. http://askubuntu.com/questions/310669/what-programming-languages-are-scopes-written-in

    2. Ubuntu SDK do not show Unity Scope project in project list

      1. apt-get remove all QT related packages and reinstall Ubuntu SDK

    3. dbus name limitation

      1. https://bugs.launchpad.net/libunity/+bug/1269256

    4. unreliable libunity-tool

      1. sometime libunity-tool can’t list all running scopes’ dbus name. we can fill its group name and unique name manually

      2. use master scope to list all results.

    5. manually add headers path and libraries to link

      1. XXXX.pro

    6. check name matched in all place

      1. config.h

      2. data/XXXX.scope

      3. data/unity-scope-XXXX.service.in

    7. who familiar Unity API

      1. Michal Hruby (mhr3)

    8. build and install. some files will be not installed if only run ‘sudo make install’

      1. qmake

      2. make

      3. sudo make install

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140114 Meeting Agenda


ARM Status

No new update this week.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   ogasawara    core-1311-kernel    3 work items   
      client-1311-xorg-general    1 work item   
   smb    core-1311-dmraid2mdadm    1 work item   
      servercloud-1311-openstack-virt    6 work items   


Status: Trusty Development Kernel

Last week we upoaded our first v3.13 based kernel for Trusty to the
archive. The most recent upload brings in a rebase to v3.13-rc8. The
AppArmor regression introduced in the original upload should already
have been resolved as well.
—–
Important upcoming dates:
Thurs Jan 23 – Alpha 2 (~1 week away)
Thurs Feb 6 – 12.04.4 Final Release (~3 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Status for the main kernels, until today (Nov. 26):

  • Lucid – Holding
  • Precise – Holding
  • Quantal – Holding
  • Saucy – Holding
    We are in a holding pattern waiting to see if any regressions show up that would cause us
    to respin before the 12.04.4 release goes out.
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html

    Note: Raring hit EOL and is no longer supported. However, the lts-backport-raring kernel
    *WILL* continue to be supported until the first point release of the next LTS (14.04.1).


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Michael

Just documenting for later (and for a friend and colleague who needs it now) – my notes for setting up openstack swift using juju. I need to go back and check whether keystone is required – I initially had issue with the test auth so switched to keystone.

First, create the config file to use keystone, local block-devices on the swift storage units (ie. no need to mount storage), and using openstack havana:

cat >swift.cfg <<END
swift-proxy:
    zone-assignment: auto
    replicas: 3
    auth-type: keystone
    openstack-origin: cloud:precise-havana/updates
swift-storage:
    zone: 1
    block-device: /etc/swift/storagedev1.img|2G
    openstack-origin: cloud:precise-havana/updates
keystone:
    admin-token: somebigtoken
    openstack-origin: cloud:precise-havana/updates
END

Deploy it (this could probably be replaced with a charm bundle?):

juju deploy --config=swift.cfg swift-proxy
juju deploy --config=swift.cfg --num-units 3 swift-storage
juju add-relation swift-proxy swift-storage
juju deploy --config=swift.cfg keystone
juju add-relation swift-proxy keystone

Once everything is up and running, create a tenant and user with the user having admin rights for the tenant (using your keystone unit’s IP address for keystone-ip). Note, below I’m using the names of tenant, user and role – which works with keystone 0.3.2, but apparently earlier versions require you to use the uuids instead. Check with `keystone help user-role-add`).

$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken tenant-create --name mytenant
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-create --name myuser --tenant mytenant --pass userpassword
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-role-add --tenant mytenant --user myuser --role Admin

And finally, use our new admin user to create a container for use in our dev environment (specify auth version 2):

$ export OS_REGION_NAME=RegionOne
$ export OS_TENANT_NAME=mytenant
$ export OS_USERNAME=myuser
$ export OS_PASSWORD=userpassword
$ export OS_AUTH_URL=http://keystone-ip:5000/v2.0/
$ swift -V 2 post mycontainer

If you want the container to be readable without auth:

$ swift -V 2 post mycontainer -r '.r:*'

If you want another keystone user to have write access:

$ swift -V 2 post mycontainer -w mytenant:otheruser

Verify that the container is ready for use:
$ swift -V 2 stat mycontainer

Please let me know if you spot any issues (these notes are from a month or two ago, so I haven’t just tried this).


Filed under: Uncategorized

Read more
Michael

Just documenting for later (and for a friend and colleague who needs it now) – my notes for setting up openstack swift using juju. I need to go back and check whether keystone is required – I initially had issue with the test auth so switched to keystone.

First, create the config file to use keystone, local block-devices on the swift storage units (ie. no need to mount storage), and using openstack havana:

cat >swift.cfg <<END
swift-proxy:
    zone-assignment: auto
    replicas: 3
    auth-type: keystone
    openstack-origin: cloud:precise-havana/updates
swift-storage:
    zone: 1
    block-device: /etc/swift/storagedev1.img|2G
    openstack-origin: cloud:precise-havana/updates
keystone:
    admin-token: somebigtoken
    openstack-origin: cloud:precise-havana/updates
END

Deploy it (this could probably be replaced with a charm bundle?):

juju deploy --config=swift.cfg swift-proxy
juju deploy --config=swift.cfg --num-units 3 swift-storage
juju add-relation swift-proxy swift-storage
juju deploy --config=swift.cfg keystone
juju add-relation swift-proxy keystone

Once everything is up and running, create a tenant and user with the user having admin rights for the tenant (using your keystone unit’s IP address for keystone-ip). Note, below I’m using the names of tenant, user and role – which works with keystone 0.3.2, but apparently earlier versions require you to use the uuids instead. Check with `keystone help user-role-add`).

$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken tenant-create --name mytenant
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-create --name myuser --tenant mytenant --pass userpassword
$ keystone --endpoint http://keystone-ip:35357/v2.0/ --token somebigtoken user-role-add --tenant mytenant --user myuser --role Admin

And finally, use our new admin user to create a container for use in our dev environment (specify auth version 2):

$ export OS_REGION_NAME=RegionOne
$ export OS_TENANT_NAME=mytenant
$ export OS_USERNAME=myuser
$ export OS_PASSWORD=userpassword
$ export OS_AUTH_URL=http://keystone-ip:5000/v2.0/
$ swift -V 2 post mycontainer

If you want the container to be readable without auth:

$ swift -V 2 post mycontainer -r '.r:*'

If you want another keystone user to have write access:

$ swift -V 2 post mycontainer -w mytenant:otheruser

Verify that the container is ready for use:
$ swift -V 2 stat mycontainer

Please let me know if you spot any issues (these notes are from a month or two ago, so I haven’t just tried this).


Filed under: Uncategorized

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20140107 Meeting Agenda


ARM Status

Nothing new to report this week


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   cking    core-1311-kernel    1 work item   
   ogasawara    core-1311-kernel    4 work items   
      client-1311-xorg-general    1 work item   
   sforshee    servercloud-1311-cloud-images    1 work item   
   smb    core-1311-dmraid2mdadm    1 work item   
      servercloud-1311-openstack-virt    6 work items   
   rtg    core-1311-kernel    1 work item   


Status: Trusty Development Kernel

We’ve finished cleaning up some DKMS packages for Trusty and are
preparing for our first v3.13 based kernel upload to the archive.
This is specifically based on the latest v3.13-rc7 upstream kernel.
I would also like to remind everyone that the 12.04.4 point release is
now taking place on Thurs Feb 6. The kernel is currently frozen for
12.04.4 and we do not anticipate any respins at this time.
—–
Important upcoming dates:
Thurs Jan 23 – Alpha 2 (~2 weeks away)
Thurs Feb 6 – 12.04.4 Final Release (~4 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

Nothing new to report this week.


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Read more
Joseph Salisbury

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20131217 Meeting Agenda


ARM Status

nothing new to report this week.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

   apw    core-1311-kernel    5 work items   
      core-1311-cross-compilation    2 work items   
      core-1311-hwe-plans    1 work item   
   bjf    core-1311-dmraid2mdadm    1 work item   
   ogasawara    core-1311-kernel    4 work items   
      client-1311-xorg-general    1 work item   
   sforshee    servercloud-1311-cloud-images    1 work item   
   smb    core-1311-dmraid2mdadm    1 work item   
      servercloud-1311-openstack-virt    5 work items   
   rtg    core-1311-kernel    1 work item   


Status: Trusty Development Kernel

The master branch for Trusty remains rebased on the v3.12.4 upstream
stable kernel. Our unstable branch has most recently rebased to
v3.13-rc4. Again, we don’t anticipate a v3.13 based upload for Trusty
until after the new year.
I would also like to point out that the 12.04.4 point release was pushed
out by 2 weeks from Jan 23 to Feb 6. This will not have any impact on
the kernel, we will still plan on shipping with the kernel we currently
have going through -proposed.
—–
Important upcoming dates:
Thurs Dec 19 – Alpha 1 (~2 days away)
Thurs Jan 23 – Alpha 2 (~5 weeks away)
Thurs Feb 6 – 12.04.4 Final Release (~7 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid

No new update this week.


Open Discussion or Questions? Raise your hand to be recognized

The next meeting will happen after the New Year. The next meeting will be January 7th, 2014.

Read more
Robie Basak

 Meeting information

 

Meeting summary

This meeting was particularly quiet, presumably due to the upcoming holidays.

Actions still outstanding:

  • gaughen or jamespage or smoser: get all server blueprints represented at /topic-t-servercloud-overview.html

Scott linked to http://kernel.ubuntu.com/benchmarking/, which he said is really nice benchmark data that the kernel team are working on.

Robie reported on the status of upstreaming mongodb armhf and arm64 portability patches.

Due to the holidays, the next meeting will be at Tue, 7 Jan 2014 16:00:00 +0000.

 

Action items

  • (carried over) gaughen or jamespage or smoser: get all server blueprints represented at /topic-t-servercloud-overview.html

 

People present (lines said)

  • rbasak (26)
  • smoser (5)
  • meetingology (3)
  • caribou_ (2)
  • jamespage (2)
  • psivaa (1)
  • hallyn_ (1)
  • smb (1)

 

Full Log

  • 16:09 <rbasak> #startmeeting ubuntu-server-team

    16:09 <meetingology> Meeting started Tue Dec 17 16:09:17 2013 UTC. The chair is rbasak. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

    16:09 <meetingology>

    16:09 <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired

    16:09 <rbasak> #topic Review ACTION points from previous meeting 16:09 * rbasak gaughen or jamespage or smoser: get all server blueprints represented at /topic-t-servercloud-overview.html (smoser, 16:04)

    16:10 <jamespage> still outstanding

    16:10 <rbasak> OK, thanks.

    16:10 <rbasak> #topic T Development Opening

    16:11 <rbasak> I’ve changed the agenda item to “T Development” for next time.

    16:11 <rbasak> Anything to note?

    16:11 <jamespage> alpha-1 this week

    16:11 <rbasak> #topic Server & Cloud Bugs (caribou)

    16:12 <rbasak> caribou_: hi!

    16:12 <caribou_> nothing here

    16:14 <rbasak> #topic Weekly Updates & Questions for the QA Team (psivaa)

    16:14 <psivaa> no updates from us as well

    16:14 <rbasak> Any questions for psivaa?

    16:14 <rbasak> #topic Weekly Updates & Questions for the Kernel Team (smb)

    16:14 <smb> nothing to report. Are there questions?

    16:15 <rbasak> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)

    16:15 <smoser> hm..

    16:15 <smoser> go back one.

    16:15 <rbasak> #topic Weekly Updates & Questions for the Kernel Team (smb)

    16:15 <smoser> kernel team has *really* nice benchmark data that they’re working on

    16:15 <smoser> http://kernel.ubuntu.com/benchmarking/

    16:16 <smoser> the data there may change formats or content, but its good too look at.

    16:16 <rbasak> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)

    16:17 <rbasak> I’ve been working on upstreaming portability patches for mongodb for armhf and arm64. This is reviewed upstream now and should land soon. Then I’ll see if I can get Debian updated to a cherry-pick of the upstream patches.

    16:17 <rbasak> No other updates. Any questions for me?

    16:17 <rbasak> #topic Ubuntu Server Team Events

    16:17 <rbasak> Christmas, I guess, is the reason why it’s quiet.

    16:18 <rbasak> Any other new upcoming events?

    16:18 <rbasak> #topic Open Discussion

    16:18 <rbasak> #topic Announce next meeting date, time and chair

    16:18 <caribou_> Ho Ho Ho

    16:19 <rbasak> Due to the holidays, I propose that our next meeting should be in January when we’re all back. Any objections?

    16:19 <hallyn_> nope

    16:20 <rbasak> So the next meeting will be at: Tue, 7 Jan 2014 16:00:00 +0000.

    16:20 <rbasak> Looks like next on the chair rota is roaksoax, so he’ll be chairing. I know roaksoax is on holiday now, so I’ll let him know by email.

    16:20 <rbasak> #endmeeting

Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)

MeetingLogs/Server/20131217 (last edited 2013-12-17 16:47:06 by racb)

Read more